[Laszlo-user] session question
circlecycle at gmail.com
Sun Apr 8 14:53:03 PDT 2007
To outline one approach
If you are using 100% server side sessions (that is, some storage
keyed to a session id) then the flash player will send cookies with
every request just like a browser. This is sufficient for my own
purposes, and it seems like dumping a state dataset back to the
server a determined points is enough to maintain state, all together
bypassing any other cookie on the server. In my own (perhaps
incomplete) take on the subject, cookies with the exception of id
strings are a hack to deal with the fact that an html page is
stateless, while laszlo applications have places to put state very
nicely via datasets.
On Apr 8, 2007, at 3:56 PM, Steven Melzer wrote:
> Another newbie question I just didn't seem to get a straight answer
> from the docs.
> I have created a signin modaldialog (thanks to everyone who replied
> to my classroot issue). The point of the dialog is to maintain the
> user has signed in through the life of the app of course. So, from
> Laszlo and the front-end this is very easy, but I am not sure I get
> how the backend session is managed.
> Since I am a Struts developer, I created a Struts back-end and the
> signin dataset, as well as every other, will go to a "dot-do".
> This works fine, but how does Laszlo accept the session information
> from the J2EE server (or just Tomcat) and how does Laszlo in turn
> send the session information back with each request to the server.
> Or am I missing my metaphors and the client should be robust enough
> to handle a stateless back-end? I read the docs and it seems
> overly complex to be managing the cookies by hand which is where
> the jsessionid lives.
> Steven Melzer
> smmelzer at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Laszlo-user