Our Development Roadmap

Never resting on our laurels, we're already looking ahead to new incremental releases, better documentation, and new full releases of Mach-II. Here's some of what's coming in the future for Mach-II.

  • Developer exchange on mach-ii.com coming soon which will allow developers to exchange modules, filters, plugins, etc.
  • New and updated documentation, articles, and quick starts
  • Official bug tracker
  • 1.6.0 maintenance release, scheduled for late Q3 / early Q4 2007
    • Introduction of granular caching mechanism
    • TracePlugin improvements for better debugging
    • Possible addition of view-handlers/view-renderers for easier repurposing of content
    • Bug fixes and other enhancements
  • 2.0 alpha release, scheduled for late Q1 / early Q2 2008
    • Big features planned

We've already  developed a working proof of concept (PoC) for a built-in caching mechanism for maintenance release of 1.5.  Since this will introduce a major enhancement, we decided to version this releast at 1.6.0 instead of the previously announced 1.5.1.  We'll release details on the caching commands, how and in what applications the caching in Mach-II should be used, and a call for feedback from you.  This release will also incorporate any bug or enhancement fixes that did not caught in the 1.5.0 release.  We understand that the new Modules features will need to evolve and be enhanced over time as people develop applications that use this feature.

As for Mach-II 2.0, we have some big features planned.  Sorry for the bait, we'll release more details when we spec it all out and no, it's not Mach-II on Rails.  We still have to get 1.5.0 into a stable release and finish the maintenance release.  As always, we will continue to use our backwards support mantra with new releases of the framework.

We hope you're excited about where Mach-II is going and as always, please let us know if you have ideas or concerns. We'll strive to make as much information available as soon as possible so we can make sure that Mach-II continues to meet your needs and introduce new features that will make your development life even easier and better.

2 Comments  |  1 Trackback  |  Announcements  |  Send
Posted 7/9/07 @ 5:00 AM by Peter J. Farrell

Comments

Will the built-in caching mechanism be something stored in Memory on the server or has there been consideration or talk of integrating Memcached(distributed memory object caching system) (http://www.danga.com/memcached/?

Thanks,

John

Posted by John Haigh at 7/13/07 12:57 PM

We haven't considered sort of distributed memory caching system at this time. Caching will happen at the event level - so it will not be advisable for all caching situations (i.e. not to replace query caching).

We've already have a simple PoC for server memory based caching with application wide caching or per user based on how that specific cache block was setup.

We're also considering a disk based caching system as well (Andrew Powell from Universal Mind has some interesting ideas on how that should work). The caching location will be configurable so it could be placed on a SAN.

Lastly, we've already gotten a request to allow custom caching systems. There appears to be a java client for Memcached, however it would require a CFC facade for some data translation and the ability to de/serialize an CFC (which is only available in CF8 from what I understand).

Posted by Peter J. Farrell at 7/13/07 1:30 PM