Caching
I hadn't been aware of the new tools that had become available for managing cache recently with newer JVMs and techniques involving multi-threading support. I just read the ColdBox wiki entry about its cache system and will be taking a closer look at those techniques soon(ish) to improve the built-in caching features in both the onTap framework as well as DataFaucet.
I would actually rather like to see this caching done as a separate project that can be plugged in as a replacement for the naive caching used in these other frameworks and that might also optionally integrate directly into one or both of the two memcached projects on RIAForge. But right now I just don't know enough about them to talk about the techniques for doing those things.
As of this past weekend I'm still working on the recent updates to other parts of the framework, better configuration and the IoC Manager which makes it a Service-Oriented (SOA) approach to CF development.
The SOA comment is interesting to me partly because it's always been the intention of the framework, but was very difficult to accomplish with previous versions. Over the years I've written a lot of rather strange and obscure code, usually to overcome some inherent limitation in the current version of ColdFusion and what I've found in retrospect is that easily a third to half of those boil down to the single limitation of not having had application-specific ColdFusion server mappings. The addition of this.mappings in application.cfc changed all that and made my long-time dream of "SOA" a real possibility...
What's really interesting though is that I had always dreamed of SOA... because until very recently I didn't know what SOA meant. I had recently read the wikipedia article on SOA and discovered that it's really what I've been trying to accomplish with the onTap framework for several years.

There are no comments for this entry.
[Add Comment]