I’m implementing long polling in Play 2.0 in potentially a distributed environment. The way I understand it is that when Play gets a request, it should suspend pending notification of an update then go to the db to fetch new data and repeat. I started looking at the chat example that Play 2.0 offers but it’s in websocket. Furthermore it doesn’t look like it’s capable of being distributed. So I thought I will use Akka’s event bus. I took the eventstream implementation and replicated my own with LookupClassification. However I’m stumped as to how I’m gonna get a message back (or for that matter, what should be the subscriber instead of ActorRef)?
EventStream implementation:
https://github.com/akka/akka/blob/master/akka-actor/src/main/scala/akka/event/EventStream.scala
I am not sure that is what you are looking for, but there is quite a simple solution in the comet-clock sample, that you can adapt to use AKKA actors. It uses an infinite iframe instead of long polling. I have used an adapted version for a more complex application doing multiple DB calls and long computation in AKKA actors and it works fine.
Note that this fromCallback doesn’t allow you to combine enumerators with “andThen”, there is in the trunk version of play2 a generateM method that might be more appropriate if you want to use combinations.
It’s not long polling, but it works fine.