[Seaside] Concurrency question

Jeffrey Straszheim jstraszheim at comcast.net
Tue Feb 19 02:07:15 UTC 2008

I think I understand.  It sounds like it will work perfectly for me.  

Dale Henrichs wrote:
> Let's be clear here. When you hit Seaside with an URL like 
> http://example.com/seaside/examples/counter, Seaside creates a unique 
> session with an ID that will be embedded in all of the dynamic URLs 
> generated from there on out for that session. If the same physical 
> users opens a new tab in the same browser and enters the 
> http://example.com/seaside/examples/counter again, they will have a 
> separate Seaside session created, that is totally independent from the 
> other session.
> If the user had clicked on the ++ link for example, she would see an 
> URL like the following 
> http://example.com/seaside/examples/counter?_s=lhDEQmkRhiXILSEU&_k=hySRdyan 
> in the browser. If she copied that URL and mailed it to a colleague 
> (or pasted it into a separate tab in the browser), then both of them 
> could issue simultaneous requests against the same session and those 
> requests would be serialized by the server.

Jeffrey Straszheim

More information about the seaside mailing list