----------------------------- Please read the FAQ! <http://java.apache.org/faq/> ----------------------------- jon * wrote: > > The simple way would be to write your data out via an OutputStream that you > then cache within the HttpSession object. Upon re-displaying that page for > the user, you could then just re-write that OutputStream out again. > > If you don't need user level caching of pages and just want something a bit > higher up, you could implement a simple Hashtable caching scheme where the > key is the query_string data and the value is the outputstream data. > > If you use ECS <http://java.apache.org/> as your outputstream, then caching > a Document object becomes trivial. > This is similar to what I am doing. I have a Hashtable called cache that I stuff pages into, based on the request.getPathInfo(). I have a finite number of pages to put in, so memory constraints don't cause a problem (yet). My doGet() method starts of by checking the cache for the page, and builds it if it isn't in the cache. At this point it is simple, but I'd surely be interested in discussing the issue with others who are doing or considering it. Thanks. -mdf -- -------------------------------------------------------------- Please read the FAQ! <http://java.apache.org/faq/> To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html/> Problems?: [EMAIL PROTECTED]
