Home

Small API change coming in release candidate 1 and Java support

  • warning: include(/tmp/fortune.txt): failed to open stream: No such file or directory in /home/mohawksoft/org/www/htdocs/includes/common.inc(1696) : eval()'d code on line 1.
  • warning: include(): Failed opening '/tmp/fortune.txt' for inclusion (include_path='.:/usr/share/php:/usr/share/pear') in /home/mohawksoft/org/www/htdocs/includes/common.inc(1696) : eval()'d code on line 1.

This week, before we spin the release candidate, a small API change will happen to the locking calls, and two new locking calls will be added.

If you've checked out the source code from CVS you'll notice that there is a new directory called "java," yes MCache will be supported under Java. While a proper HttpSession interface will take a while, the underpinnings for it should happen sooner rather than later.

The issue to be "fixed" is an optimization of the locking protocol which will allow an MCache client to locally cache their data. This will allow the Java HttpSession to use it's own internal cache when creating sessions, and only report changes. This could also lead to a way to optimize PHP session handling.

MCache will remain the central locking registration and holder of the data, but will allow client applications to lock with their version number of the data. If the version on the server is different than that on the client, MCache will send the data. Otherwise, MCache will process the lock and return "OK" without the data. This can increase performance of the MCache as well as the client (assuming moderate stickiness of the load balancer.)

»