> ...but not with this. No amount of lazy navigation macros will prevent > you from generating the front page, which in many cases will be > expensive to generate. I'd like to have a pre-generated cached version > for clients without a session (they all get the same content anyway) and > actually generate a new widget tree only when an action request comes > in. You don't need to generate a per-session widget tree for pages > accessible via navigation widgets, for example.
JT Yu is working on a generalized memoization library that will help implement those things. Why does your frontpage rely on database access or other expenesive things if you want it to be cached anyway? I'm not sure I'm getting the entire point here. > I suspect (2) was a way of dealing with hunchentoot's URL rewriting, > which gets in the way unless you turn it off. But it's not supposed to jump in when cookies are supported... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
