[Seaside-dev] Issue 184 in seaside: cached configurations on Session

[codesite-noreply at google.com]

Issue 184: cached configurations on Session
http://code.google.com/p/seaside/issues/detail?id=184

New issue report by jfitzell:
We discussed at one point having a CachedConfiguration class and putting
one on Session. It would cache the result of any preference lookup, which
would significantly reduce the number of searches through the configuration
hierarchy.

This would obviously mean that all preference lookups would want to go
through the session (which makes logical enough sense) but also that
configuration changes to the application might not take effect in existing
sessions (possibly good or bad depending on your point of view).


Issue attributes:
	Status: Accepted
	Owner: ----
	Labels: Type-Feature Priority-Low

-- 
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