Thanks again for your help. If I call this ! ShutDown in my CometActor, it will redirect me back to the home page once ShutDown is received.
Did you want me to open up a ticket for this? Thanks, Bradford On Apr 23, 10:06 am, bradford <fingerm...@gmail.com> wrote: > Thanks, David. What haven't you thought about?! > > On Apr 23, 9:57 am, David Pollak <feeder.of.the.be...@gmail.com> > wrote: > > > On Thu, Apr 23, 2009 at 6:45 AM, bradford <fingerm...@gmail.com> wrote: > > > > Thanks, David. I will play around with this when I get home. I'll > > > open up a ticket at the same time as well, when I have sufficient time > > > to review the problem. I'm looking to have the comet actor > > > automatically shutdown after it's pushed the 10th item to the server, > > > which looks like would be possible to do with a shutdown function. > > > You can manually shut down your comet actor today. Just do a "actor ! > > Shutdown" and it will release its resources and unregister from the session. > > > > Something I stumbled upon in my search: > > >http://cometdproject.dojotoolkit.org/documentation/FAQs/multipleTabs > > > Lift detects this too and will "ping-pong" the long polling from multiple > > windows... more HTTP requests, but lots of responsiveness. > > > Chrome and FF 3.1+ do not have this 2 connection limit. Lift will (at some > > point before 1.1 is released) do proper browser detection and not enforce > > the 2 connection limit for these browsers (because they don't have the > > limit). > > > Further, you can set Lift up to do the Comet polling on a randomly named > > host such that each window/tab gets its own host (with DNS wildcarding) to > > poll on and in that situation, you also work around the 2 connection limit. > > > > Thanks > > > > On Apr 23, 9:12 am, David Pollak <feeder.of.the.be...@gmail.com> > > > wrote: > > > > On Wed, Apr 22, 2009 at 6:53 PM, 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? > > > > > Each CometActor has a name. You can have multiple CometActors with > > > > different names that represent different components. In the Lift chat > > > > example on the Chat page, there are two separate components. The second > > > one > > > > is identified with: > > > > > <lift:comet type="Chat" *name="Other"*>Chat Text</lift:comet> > > > > > Please note the "name" attribute. > > > > > For each page that you render, you can write a snippet or something that > > > > does: def myNextCometGuy = <lift:comet type="Chat" > > > name={randomString(20)} > > > > /> > > > > > The big issue will be closing the comet actors down. I've been planning > > > to > > > > put an optional timeout in CometActors (basically allow them to shut > > > > down > > > if > > > > they haven't had a listener attach to them in N minutes.) If you need > > > > this feature, please open a defect athttp:// > > > github.com/dpp/liftweb/issues > > > > > Thanks, > > > > > David > > > > > > Thanks, > > > > > Bradford > > > > > -- > > > > Lift, the simply functional web frameworkhttp://liftweb.net > > > > Beginning Scalahttp://www.apress.com/book/view/1430219890 > > > > Follow me:http://twitter.com/dpp > > > > Git some:http://github.com/dpp > > > -- > > Lift, the simply functional web frameworkhttp://liftweb.net > > Beginning Scalahttp://www.apress.com/book/view/1430219890 > > Follow me:http://twitter.com/dpp > > Git some:http://github.com/dpp --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
