Thanks for this - I'll look into it. I seem to recall seeing something about this on my Google travels.
I think it comes down to the usual issue of priorities. Sometimes response time is my priority, so I lean towards keeping the in-memory Document cache - other times (web server) memory space is the priority, so I lean towards puking the text out to DB/file then reading back in. I wondered if there was some magic way to puke the Document to DB/file then read it back in in Document form (rather than having to parse the text). Then I started to use XMLFilters - so I found I needed to re-parse the text anyway! (Is there any way of applying filters to a Document rather than to the String version?) Best regards Chris > > doesn't know if it is relevant with a XML Document cache, but > you should take a look on WeakReference. you could implement > a least recently used cache set with WeakRefences on > documents. it sounds like an entertaining thing to do :) regards > > Nicolas ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_idP47&alloc_id808&op=click _______________________________________________ dom4j-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dom4j-user
