I came up with the idea of an window ID passed as request header from
browsers. Ben Galbraith, with whom I discussed this on JavaOne, sent
me to this usenet list.
The problem is that cookies including session cookies are shared
across all browser windows. This prevents web application developer to
store things in a session for many use cases as one window would
overwrite the values of other windows. This could easily be solved
with a window id passed as request header from the browser. A window
ID is just a unique random number.
In HTML 5 this problem is already addressed for the client side with a
sessionStorage. I would like to have this solved for the server side
I contacted sofar developer of IE, sent a mail to the mailing list of
webkit to reach Chrome and Safari and filed the following bug to
I tried to explain the problem in more details in my blog. In addition
wrote a sample application which shows what we could do with a window
I would appreciate your feedback.
Best Regards / Viele Grüße
For example, Dojo sends a client id header:
around this problem, this is correct. My sample application uses
But it stays a workaround and has trade offs. The cleanest approach
would be a window id sent by the browser.
On 9 Jun., 18:34, Dion Almaer <d...@almaer.com> wrote:
> Just a short FYI.... libraries have stepped up here to give devs this
> For example, Dojo sends a client id header:http://www.sitepen.com/blog/2009/02/27/deterministic-clientserver-int...
> > I would appreciate your feedback.
> > Best Regards / Viele Grüße
> > Sebastian Hennebrueder
> > -----
> > _______________________________________________
> > dev-platform mailing list