In the first part of the cache blog entry we looked at how we can use the cache directly without entering into great detail. Now let's have a look at what the cache is at capable of. Because it provides much more than just storing data.
Since version 3.1.2 Railo supports the possibility of using a cache. This blog entry will go into the details of this feature.
The blog is divided into 3 parts, the first part will deal with the base functionality, the second part show how the cache is used in backend and the last part takes care of specialties when using the cache and shows a reference.
I'm actually hesitant to post this because the Railo team is actually trying to make progress on documentation and we have some new documentation policies in place. However, I know if I don't post this and people eventually find out about it, they'll wonder why they didn't know sooner. This tip pertains to Railo's createObject('java') implementation. I'm told that it has been there for awhile, but I couldn't tell you what build it came from. I'll share the code and go from there.
<cfset object = createObject('java','path.to.package.classtoinvoke','/path/to/jar/file/on/system')>
Read that line 2 or 3 times and let it sink in a little. Yes, Railo's createObject('java') has a 3rd (and 4th) argument. This is the full documentation on this from Michael is:
createObject('java',String className,String paths, String delimiter )
- 'java' (required)
- className (required) - the full class name (class and package) of the class to invoke.
- path (optional) - a list of jar files and directory that contains class files
- delimiter (optional) - delimiter used for the path list (default is comma ",")
Sean Corfield will be presenting this to the opemcfml.org advisory board, whether it gets voted on or not remains to be seen. Also, please note that I'm making Documentation/Wiki a high priority for the year 2010.
I have just uploaded Andrea Campolonghi's current RC version of the ajax built in tags. Here's what you need to do in order to install and test the tags.
This is something we wanted to do for more than a year now. We wanted to implement a cache that is reachable from all the servers in a cluster. So here we go...
GetRailo.org was recently given a uservoice.com account and we're taking full advantage of this! If there is a future enhancement you want the GetRailo.org Development Team to consider or you want to drum up votes for a particular feature then go draft up an idea or vote on an existing one! You can do so by checking out the community section of GetRailo.org and using the "feedback" widget or you can go directly to railo.uservoice.com.
The task manager and the synchronization feature (including the cluster scope) are some of the most useful background changes we have made in Railo 3.0. They allow you to use Railo for background activities and help you configure clustered Railo instances.
As you might have read in my previous entries, Railo 3.0 introduces some new multimedia tags and functions. In this blog entry I will show you how to use them.
With the release of Railo 3.0 we have built a Amazon EC² image which allows you to create your own running instance of it.
Before I post part III of Railo 3.0 release entry, just a quick one on how to update Railo from one version to a newer one.
