It's not really the same thing though as a Akka `props` method, since this isn't an actor, and it's on an object that might have nothing to do with actors.  And it might return null, we definitely don't want it to be confused for a normal Akka `props` method.  So, in the context of this being a WebSocket, if it's just called props, props for what?  Why would a WebSocket have a `props` method on it?  `actorProps` makes it clear that this is for if this WebSocket is being handled by an actor.  Also, this isn't intended to be public API, if there was a way to nicely scope it to just be accessible from the `play` package as there is in Scala, I would do that.