On Tue, Nov 4, 2008 at 10:34 PM, Mark Ramm <[EMAIL PROTECTED]>wrote: > > But it's harder to figure out how this could work with Beaker for > regular session data, but I think it might be possible to write > something that set's response headers when you call .save() on the > session dictionary, and thus provides an alternative beaker back-end > which works with apache sessions. >
quoting from : http://httpd.apache.org/docs/trunk/mod/mod_session.html "At the core of the session interface is a table of key and value pairs that are made accessible across browser requests." Since this is basically what Beaker provides, and since Beaker has sort of a pluggable storage backend system, making this look like a Beaker session seems the obvious choice. > > I'm a bit hesitant to break backwards compatibility with the current > Beaker API, since there is a good amount of time/thought/energy > invested in that at this point. > > How would this break the API? Wouldn't this look pretty much the same from the user's (coder's) perspective? Am I just missing something? Kevin Horn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
