Browsers do not make any distinction between tabs or new windows. Currently if you have 2 or more tabs, essentially Lift is getting multiple Comet requests per same session it will respond immediately to the browser to avoid connection starvation.
The problem with your use-case is that server simply gets the same session ID and can not tell the difference between on tab or another. We do have a unique page ID so different tab suppose to have distinguished page ID-s but I don't think this will help a whole lot. CometActors being asynchronous components when processing a message (comming from other actors potentially) it can not tell to which page the COMET response will be served. Br's, Marius On Apr 23, 4:53 am, bradford <fingerm...@gmail.com> wrote: > I noticed in the chat demo that if you enter your name or chat into > one tab, the same results will propagate to the other tab. I need a > short lived comet session that's unique to each tab -- I want to > prevent one tab from mixing its data with another tab. I understand > that most user browser only allow for 2 HTTP connections at a time, > but as I said, I have about 10 consecutive pushes to the server that > I'll be making and then I want the comet connection to immediately > terminate. > > Is this possible to do with the existing lift CometActor? If so, any > suggestions on where to begin? > > Thanks, > Bradford --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
