On Monday, April 28, 2014 11:46:22 PM UTC-4, Bert JW Regeer wrote: What are you using the session ID for?
Performance logging (session_id into statsd and logs). Unit Testing. Integrated Testing. Automated Test suites. Development Troubleshooting ; Production Customer support. Often times we need the actual SessionID, which is used as the storage backed identifier, to access the stored value. It's annoyingly complicated to working around this with custom classes and monkeypatches for each session-ing option. Beyond that, I can't make this clear enough... Personal opinions on Interfaces / Client vs Server / etc aside... I'd like to talk about common expectations : 1. Server Side Sessions are historically common across the internet. Server Side Sessions are basically how shit got done for decades. Developers expect them. Jump on StackOverflow and you'll see thousands of questions across a variety of languages for people talking specifically about the session_id. 2. How other popular python projects deal with session ids: Beaker Session ( used in Bottle, Turbogears, Pylons ) .id Cherrrypy .id Django: old - request.session.session_key new - request.session._session_key Flask: .sid plone getBrowserId() tornado no standardized session support multiple endorsed addons provide session support , all seem to provide id but differently web2py response.session_id werkzeug .sid web.py .session_id webapp2 .sid zope: externally getClientId internally client_id Pyramid appears to be the ONE AND ONLY python web framework that supports sessions BUT does not support a session_id. In fact, as stated above, the core developers oppose supporting a session id. I don't mean to disagree or address any of the rationales/reasons mentioned above against supporting the session id. Many of them are very good and sound. However, if you want to know why this question comes up often , why it will continue to come up often and -- potentially -- why some people might be turned off by pyramid... it's the list above. What is simple, normal, expected, trivial and standard across many frameworks is an "advanced topic" in Pyramid and left to developers to deal with on a per-project basis. Pyramid is the least opinionated framework for just about everything -- but sessions. -- 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/d/optout.
