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
I therefore am paying attention to caching, but not necessarily
designing and implementing a caching framework from scratch.
I think your PROBLEM statement misrepresents WebKit development when it
says that developers have to start from scratch or go without. I do
neither.
I'm not saying that your caching framework ideas don't offer some
bonuses over "caching in object attributes", just that the PROBLEM
statement is too strong.
In any case, good luck. It will be interesting to see if you and Terrel
collaborate on this. If you haven't read this yet, you should:
http://jaguar.sourceforge.net/cgi-bin/wiki/DependencyManagementService
I'm certainly open to tweaking and refactoring WebKit to support a good
CacheKit.
-Chuck
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss
