On Wednesday, July 15, 2015 at 11:40:08 AM UTC-7, Massimo Di Pierro wrote: > > [...] > Each client must have a unique token and pass it in the ws:// connection > string when it connects. If it up to you to make up tokens. They can be > random numbers, uuid, etc. You have to give a token to the clients and you > have to register the tokens with websocket_server via the /token api. >
For instance, with web2py you enforce user login (@auth-login-required), and when the login succeeds you generate a token (e.g., uuid.uuid4()), perhaps adding it to the session data and using it when accepting message forms? /dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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/d/optout.
