@rkuhn The problem with Actors.websocket, is that that Actors class is part of ReactiveMaps, not part of Play.  So that would work fine if this class was part of ReactiveMaps, but the intention is to pull it out of ReactiveMaps and put it in Play.  In Play so far, there are no actors, we provide an actor system that gets lazily created if you use it, but we don't do anything with it.  So we need to come up with a way of creating that actor, and making it available to the WebSocketActor creation code.  But the best way to do that is hard to answer now, because we don't know what it's going to look like when we move to akka-http - there are a lot of unanswered questions with the move to akka-http, for example, how many actor systems we will need (I think we will need two, in order to be able to restart the users actor system on reloads in dev mode but still maintain active akka-http connections).