Wim Dumon wrote: > Compare it to what google does in e.g. gmail: when you hit refresh, > you clearly see that the entire application is reloaded. Eventually > you arrive in the same location were you where, through what was > entered in the address bar. But the session is restarted.
Right, but that then has to rely on the URL to take you there. If a cookie was used to mark the location, then every tab would be taken to the same place. > Wt makes a distinction between a session (or a session cookie, if > used) and a user-logged-in cookie. It's natural to have a logged-in > cookie, since that is normally shared between all tabs in a browser. I've seen that sort of behaviour, but I'm not sure it's right, since I've seen it cause all sorts of problems too. Often I want separate tabs open to different places on a website - if they share a cookie it too often results in each tab seeing exactly the same view after a refresh. Maybe I've got several logins to a site, for different purposes, and I want to have them all open at once. I've also seen terrible confusion when different businesses share a common back end service supplier, and expect people to have separate accounts, while the account keeping is in the common back end. > The session tracking mechanism is intended to keep two different > instances of your application separated. Compare again to gmail: you > don't need to log in if you hit reload or open it a new tab. > But as I already said: there is also a method in Wt to not create a > new session on reload, but then you have to accept that there is a > visible session descriptor in the URL. Sure - that seems to be a limitation imposed by various web technology assumptions. The idea of tabs and logins simply hasn't been very well though out in my opinion, hardly surprising given the simple intentions of the original www. Graeme Gill. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
