Thanks Roland. That's awesome.

> On 1 Apr 2014, at 8:57 pm, Roland Kuhn <notifications@github.com> wrote:
> 
> In documentation/manual/javaGuide/main/async/JavaWebSockets.md:
> 
> > +The actor that we're sending to here in this case looks like this:
> > +
> > +@[actor](code/javaguide/async/MyWebSocketActor.java)
> > +
> > +Any messages received from the client will be sent to the actor, and any messages sent to the actor supplied by Play will be sent to the client.  The actor above simply sends every message received from the client back with `I received your message: ` prepended to it.
> > +
> > +### Detecting when a WebSocket has closed
> > +
> > +When the WebSocket has closed, Play will automatically stop the actor.  This means you can handle this situation by implementing the actors `postStop` method, to clean up any resources the WebSocket might have consumed.  For example:
> > +
> > +@[actor-post-stop](code/javaguide/async/JavaWebSockets.java)
> > +
> > +### Closing a WebSocket
> > +
> > +Play will automatically close the WebSocket when your actor that handles the WebSocket terminates.  So, to close the WebSocket, send a `PoisonPill` to your own actor:
> > +
> It will be in my upcoming book ;-) We should also add these to the documentation, creating ticket.
> 
> —
> Reply to this email directly or view it on GitHub.