hi,
just wondering how to take the next leap forward with lift. i've coded
the timer app, as well as the chat room. then i read about how lift
needs session affinity, and was wondering what were the best practices
around pushing shared state (i.e. not having a singleton chat room on
one webapp that all browsers subscribe to) through lift/comet.
basically, how to solve pub/sub where browser clients need access to
shared state. is akka the preferred route?
btw, does lift support non-
browser comet? i.e. a way to open up a long-poll or websocket without
using a browser accessing a lift front-end?
still a bit new to lift. any thoughts would be appreciated.
--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.