On Tue, Feb 18, 2014 at 11:00 AM, Jonathan Vanasco <[email protected]> wrote: > > >> "B" just needs some cookbook examples. And I think Pyramid's session >> infrastructure needs to support session IDs. Not as a requirement for >> all backends, but as support for the backends that want it so they >> don't all have to reinvent the wheel. I'd like the 'session.id' >> attribute to be standard, although that may be too much. (Currently, >> my code uses 'getattr(session, "id", None)' to determine the session >> ID and whether the backend supports that kind of ID. Perhaps it should >> be 'session["id"]'; I'm not sure, but Beaker uses 'session.id' and I >> think pyramid_redis_sessions does (?). > > > +100 > > I created an issue 12 months ago, which was rejected and closed -- > https://github.com/Pylons/pyramid/issues/895 > > ISession needs to support proxying the session id from backends that support > it.
Pyramid needs *something*. I'm not sure what yet. I think it needs a function to generate a session ID, and instrunctions about how to manage the ID. I'm not sure if that needs to be in ISession itself. 'signed_serialize()' is just a function, There could also be an optional method on BaseCookieSessionFactory or SignedCookieSessionFactory, because you can't really have sessions without the ID in a cookie. Although it would be nice to have an .id attribute on ISession; then backends that don't support ID's could just set it to None. Then callers would know definitively that there's no session ID. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/groups/opt_out.
