On May 13, 10:06 am, Benigno <bca...@albendas.com> wrote: > We have made an app with web2py to present data from a home-automated > home as a web service. There is a certain hardware at the home that > sends all the information that transverses the bus into our server, > and from there on, we process and present the data using web2py.
I am doing something similar. My client is a daemon process. Upon my first contact with the server, the daemon client provides an authentication key. This is checked in the web2py DB. If found/ valid, a session number is returned to the client (inside a cookie). The client stores this cookie, and returns it to the web2py server, as a cookie header, on each subsequent access. This maintains the session. So far, this strategy appears to be working well. All functions in the controller used by the daemon process have an "IsLoggedIn" decorator, which checks first. Depending on the specific details of your situation, you could extend the valid time of the session from the default value. I don't know the value of that default offhand.
