You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While we've been thinking about the web apps as things that happen on one page, that's not a very general model. Consider something like amazon, that you can log into and move between pages.
Similarly, we need to be able to initialize argon and then move between pages without losing the state of the system.
Perhaps some kind of use of cookies or something will facilitate this. If it was just about "state" (that can be reset quickly) you could imagine this would fall on the client/server app (like Amazon); but, things like vuforia take far to long to "set up again". Plus, we want a way for the apps to behave smoothly as they move from page to page, with no extra flashes or whatever.
Perhaps something simply like having a bit of data that could be stored in a cookie, and if you supply this data to argonInit, the state of the web page is maintained from page-to-page in Argon4? Perhaps even on non-Argon4, argon.js could store the client state somewhere so it could re-create things?
The text was updated successfully, but these errors were encountered:
While we've been thinking about the web apps as things that happen on one page, that's not a very general model. Consider something like amazon, that you can log into and move between pages.
Similarly, we need to be able to initialize argon and then move between pages without losing the state of the system.
Perhaps some kind of use of cookies or something will facilitate this. If it was just about "state" (that can be reset quickly) you could imagine this would fall on the client/server app (like Amazon); but, things like vuforia take far to long to "set up again". Plus, we want a way for the apps to behave smoothly as they move from page to page, with no extra flashes or whatever.
Perhaps something simply like having a bit of data that could be stored in a cookie, and if you supply this data to argonInit, the state of the web page is maintained from page-to-page in Argon4? Perhaps even on non-Argon4, argon.js could store the client state somewhere so it could re-create things?
The text was updated successfully, but these errors were encountered: