On Wed, Feb 19, 2014 at 1:43 PM, Jeff Dairiki <[email protected]> wrote: > On Wed, Feb 19, 2014 at 12:54:04PM -0800, Jonathan Vanasco wrote: >> I think you'd need to have an `id` in ISession as an attribute. > > If I understand your motives -- it's quite possible that I don't -- you > want access to the session id in order to access extra "externally > stored session data" (e.g. from SQL) which is not handled > automatically by whatever implementation of ISession you are using. > > In that case, why does your external storage key have to be the same > as the ISession implementation's internal id (if indeed there is one)? > Why not just generate your own key for the external storage, and save > that in the session as a normal session variable?
That could work, actually. I need something in my access log to indicate which requests form a session, and I was using the session ID because that's what it's for. But I could generate a different ID if my key isn't present, and that could have some advantages. I could make it int and autoincrement which would me more convenient than a random string, and it would also give the user an extra level of privacy. So thanks for the idea. -- 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.
