|
Title: Need strategy advise: HTTP User Sessions rtcHTTPServer Post by: craigism on October 06, 2013, 10:01:59 PM I already read THIS (http://www.realthinclient.com/sdkarchive/index2d622d62.html) and THIS (http://realthinclient.com/sdkarchive/indexeadceadc.html).
I also know that I will be dealing with rtcDataProvider. My App is browser based and is a HTML5 + JavaScript and makes light use of the server. There will be under 10 users max. Usually one or two users. From what I understand: I think that I will set a long session timeout (about 3 hours). I also think that I will use a cookie or other local storage for remembering the user\session. All my data is safely stored client side in a HTML5 App so I'm only doing this to avoid having the user "log-in" many time within the same day. My question is should I use the built in session support or should I roll my own user management? I have 8 rtcDataProviders (each for groups of server side functions) and I'm looking for a solution that I can put in a shared event so I can reuse the code for all the rtcDataProviders. Related session question: Why does a single user session seem to open up more than one session? Thanks. Title: Re: Need strategy advise: HTTP User Sessions rtcHTTPServer Post by: Kevin Powick on October 06, 2013, 10:45:51 PM We tend to avoid using cookies because:
-- Kevin |