On Tue, Feb 24, 2009 at 8:05 AM, Leslie P. Polzer <[email protected]> wrote: > What are your plans for implementing this? I can't commit to a timeline, unfortunately. There are a couple of things I'd like to see happen in weblocks - this, a jQuery rewrite (it's just more practical than Prototype at this point), and support for caching. I'm not sure when and in what order I'll need these things yet, so the only thing I can say is that I'll probably do them eventually. Sorry, that's the best I can do now.
Btw, here's my idea for caching: (defun get-foo (...) ...) (defcache get-foo :request) (defun get-bar (...) ...) (defcache get-bar :application :timeout 5) This way get-foo will only get called once per request (the other times the cached value will be returned immediately) and the result of get-bar will be cached accross the application and will not be called more often than every 5 seconds. You might want to know why cache in the request. This can become very comfortable - for example, dataseq calls dataseq-data many times for a single render. Instead of refactoring dataseq to call dataseq-data only once and cache the value manually, we can simply use the defcache macro. Defcache would be implemented in a somewhat standard fashion - the way CL people normally implement defmemoize. It's probably too many ideas for a single thread, but that's what I have on my mind and todo list. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
