its not about the browsers each browser has its own unique session the problem is the tabs of one and the same browser - they all share the same session. so if you have for example 3 open tabs of the same website, they will most certainly intefere with each other. thats why I consider it a nogo to use sessions with captchas (if they just override each other) or any other such thing that will easily run into collisions. it's a misusage of sessions and damned to blow up.
I dont know any techniques which would enable you to distinguish different tab sessions but maybe someone else does. usually the session/cookie cannot know which tab is which. On 19 Nov., 19:18, Daniel <danwgr...@gmail.com> wrote: > I have used $this->Session->write and $this->Session->read to pass > data around my Cake app. The problem with this method is that the > user could have two or more browser windows on the go and a session > variable could get overwritten. I was wondering if there is a way of > preventing this, like using some sort of browser ID to prefix the > variables name? > > I have also used parameters in the URL to pass data. I was also > wondering whether there are any other techniques and which is the best > technique. > > Thanks. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
