[Seaside-dev] Issue 167 in seaside: Evaluate WACache expiry branch
for inclusion
codesite-noreply at google.com
codesite-noreply at google.com
Sun Sep 21 18:01:00 UTC 2008
Issue 167: Evaluate WACache expiry branch for inclusion
http://code.google.com/p/seaside/issues/detail?id=167
New issue report by jfitzell:
This should be done before Alpha ideally, as it may result in WASession
being changed to inherit directly from WARequestHandler. As long as the
basic approach is sound further development can continue during alpha.
I'd like a few comments on the approach before going further with it. See
the -cache branch (and possibly the -expiry branch, though I think the
-cache one is the better approach).
Issue attributes:
Status: Accepted
Owner: ----
Labels: Type-CleanUp Priority-Medium Milestone-2.9alpha Version-Seaside2.9
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
More information about the seaside-dev
mailing list