okay ... let me give you a quick run down on all the cool stuff that has
just been released in this nightly build.
Caching .....
Right, in light of the recent discussions regarding caching, i decided
to go back to this area and look at what others were doing and bring us
inline. We were already nearly in line (such is the woes of being the
first, then others not copying you!).
The caching functions have been rounded out to be compatible with others
as you can see the list of functions here:
http://www.openbd.org/manual/?/function/category/cache
We've taken to the notion of "region" (which we called group) and
applied to that everything. So now you can use as your caching engines:
* Memory
* Memory + Disk
* MongoDB
* Memcached
* Couchbase
* Amazon ElastiCache
It is dead easy to add more storage engines if we want to. At this
point i don't see a need for another one outside of these heavy hitters.
We've extended functions like SalesForceXXX(), CFQUERY and
CFCACHECONTENT to use these new region format, so allowing you to
quickly use say a Memcached server for your query requirements.
In addition, we also added caching to CFFUNCTION, so you can now also
cache these calls, using the same region="" attribute to determine which
storage engine you are going to be using.
http://www.openbd.org/manual/?/tag/CFFUNCTION
For a full down on all the configuration etc then go here:
http://www.openbd.org/manual/?/caching
Want more goodness? okay then ...
Session management across multiple machines is a pain, and this is an
area that to be frank has been poorly supported by the underlying J2EE
engines (esp as some of their techniques simply do not work in the cloud).
OpenBD now lets you specify a session storage engine for where it will
store its sessions. Again MongoDB, CouchBase/Memcached are supported
for this.
http://www.openbd.org/manual/?/app_application_cfc
We are using this particular feature in the cloud, using Mongo as our
session storage engine, and it rocks.
For those from the old skool, think of this like 'client' scope without
the performance overhead and done right. Kept nice and simply and
tuned to ensure only the minimal amount of data is going back and forward.
We rewrote the session layer here, improving performance overall.
Want more? okay ...
Managing JSON with remote AJAX frameworks can be a pain when it comes to
the callback on the access=remote on CFFUNCTION. We've taken the pain
out of this, but allowing you to specify the case of the JSON keys and
format of the date through either control parameters or by specifying
them on the CFFUNCTION itself:
http://www.openbd.org/manual/?/webservices_restlet
http://www.openbd.org/manual/?/tag/CFFUNCTION
You can also control the default behaviour using the bluedragon.xml file:
http://www.openbd.org/manual/?/engine_bluedragonxml#jsoncase
http://www.openbd.org/manual/?/engine_bluedragonxml#jsondate
oooh and just one more thing .... we've added the SalesForce plugin to
the core engine, so there is no more requirement to add that manually.
http://www.openbd.org/manual/?/plugin_salesforce
PHEW! That was a lot. We're putting on the final touches to our new
web site and a round of last feature requests that have come in that
we'll be adding in before we spin out 2.3 officially. We also have some
REALLY cool coming up which once our team have put their CSS touches on
it, you will see the new inbuilt profiler.
Enjoy
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
