8. WebSockets and Actors | Mastering play framework for scala

Closing a WebSocket

When the WebSocket is closed, Play automatically stops the actor bound to it. This binding works in two ways: the WebSocket connection is closed when the underlying actor is killed. If there is a need to free any resources once the connection is closed, we can do so by overriding the actor's postStop method. In our example, we have initialized a DBActor within WebSocketChannel. We will need to ensure that it's killed once the WebSocket is closed, since each connection to the WebSocket will lead to the initialization of a DBActor. We can do so by sending it a poison pill, as shown here:

override def postStop() = {
  backend ! PoisonPill
}

Using FrameFormatter

Suppose that an incoming JSON has the same fields for every request, instead of parsing it every time; we can define an equivalent class in this way:

case class WebsocketRequest(reqType:String, message:String)

Now, we can define our WebSocket to translate the JSON message to a WebSocketRequest automatically. This is possible...

Tech Concepts

Programming languages

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Mastering play framework for scala

By : Saxena

Mastering play framework for scala

By: Saxena

Overview of this book

Closing a WebSocket

Using FrameFormatter

Mastering play framework for scala

By : Saxena

Mastering play framework for scala

By: Saxena

Overview of this book

Closing a WebSocket

Using FrameFormatter

Confirmation

Buy this book with your credits?

Submit Your Feedback

Create a Free Account To Continue Reading

Sign in to activate your 7-day free access