For our application I want to not only cache from memory, but also store the objects on the fileSystem (as the cost of generation in our app can be high). With the change so that items are only written to the file system when the number of memory objects reaches max and this.free() is called it seems that we loose this capability unless we set the memory objects to a small number (which defeats the objective of the cache and having lots of memory). One of the benefits of the old way was that if the VM unexpectedly quits we had the file system cache for all the items that were in memory. Also all memory objects are lost after shutdown, maybe it would also be also a good idea to write the memory objects to disk on a formal shutdown (this was not needed with the old method) if the queue method is not returned.
Comments? Rgds CB > > > froehlich 02/01/27 05:14:40 > > Modified: src/java/org/apache/cocoon/components/store > MRUMemoryStore.java > Removed: src/java/org/apache/cocoon/components/store > FilesystemQueueObject.java > FilesystemQueueImpl.java > FilesystemQueue.java > Log: > you'll hate me for that but had to change some things, because > there were too much issues with that: > a) changed the swapping algorithm. Objects are only written to fs > method in the free() method of the MRUMemoryStore > b) therefore no need of the FilesystemQueue. Because there were > much less writing to fs. > c) removed the configuratioin section in the cocoon.xconf file > d) add "isDebugEnabled()" > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
