Hi,
In one of my modules I'm trying to create a local socket connection that
persists across a single session (one socket per one user logged into the
system from a given browser), and thought that current.session would give
me the info I needed. Specifically, we use a lot of REST calls in our
frontend code to populate data for certain elements on the screen and this
creates a new session hash for the current.session each time, but the
actual session is the same. The only way I've been able to get a key that
identifies the session is to run:
cookies = current.request["cookies"]
session = cookies["session_id_<appname>"].value
Shouldn't some identifier (or even this cookie itself) be available in
current.session? Perhaps I misunderstand the point of current.session.
Matt
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
