On Sunday 31 March 2002 05:56, Chuck Esterbrook wrote: > On Sunday 31 March 2002 01:46 am, Tavis Rudd wrote: > > PROBLEM > > There is no standardized way to cache output in WebKit. �As a > > result, Webware developers have to start from scratch when > > designing and implementing caching framework for their > > application, or they just ignore the benefits of caching. > > I use this kind of caching all the time, which I find very easy and > a good "bang for the buck": > > def foo(self): > if self._foo is None: > self._foo = whatever() > return self._foo
That's great for partial output caching, but not necessarily for full-page output caching. You can do full-pages this way, but it's not very efficient. WebKit still has to do a fair bit of processing just to get to the servlet and this approach stores 10 or more copies of the page output in memory because of the number of live servlet instances. What I'm proposing would shortcut the URI-to-servlet mapping process and store only a single copy. Yeah, that PROBLEM statement is a bit strong. How about this instead? There is no standardized way to cache **full-page** output in WebKit. As a result, Webware developers have to start from scratch when designing and implementing caching framework for their application, or they just ignore the benefits of caching. _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
