From: Brian G. <br...@qu...> - 2004-05-24 13:28:54
|
You've addressed half of Lars' question -- the caching infrastructure -- but not the other half -- the integration of caching into the template language. The approach taken by OSCache is quite cool, in that allows JSP writers to specify the interaction of caching and content quite nicely. > Caching has been discussed a lot and there is a caching provider > interface so you can write your own caching implementation. (As I have > done). > > To cache individual objects, you can use a global service model to cache > individual templates (eg, connection.wmt, statements.wmt, etc.) and > objects (queryResultReference, queryResultDomain, > queryResultTransaction, etc). With this kind of a model, you cache both > the template elements and the results according to memory and > invalidation events. |