I don't know enough to know if there's any way to save a session id persistently over AMD requests.
What about using cookies? Would that be a possibility to save a session id on the client side to identify the session?
I considered cookies, but I don't think they're as reliable as I would like. People can disable cookies in their browser. Isn't the JSON option like server-side cookies? I went this route and it seems to be working. An added bonus is being able to persist across sessions so one can resume in the space that one left last time.
Are there concerns about using the JSON approach? It seems pretty secure, but I'm not a student of security best- practices.
@C0Rrupt Use Web services
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.