Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Optimized WebSocket Broadcast

DZone's Guide to

Optimized WebSocket Broadcast

· Integration Zone ·
Free Resource

Continue to drive demand for API management solutions that address the entire API life cycle and bridge the gap to microservices adoption.  Brought you to you in partnership with CA Technologies.

Originally authored by David Delabassee

"When you have to make a choice and don't make it, that is in itself a choice."  ( William James)   Tyrus logo

The Java API for WebSocket (JSR 356) is one of the APIs recently added to Java EE 7. It is a '1.0' release, which means that the API is complete and fully functional. It is often said that premature optimization is the root of all evil, so an initial implementation can easily be optimized. The same is also true for features.  Choices had to be made since it is impossible to implement all the desired features in an initial release. Clearly, there are different aspects that could easily be improved going forward.

Tyrus serves as the JSR 356 Reference Implementation.  It is also a test-bed for potential new WebSocket features and improvements. As always, a proprietary feature of an implementation doesn't necessarily means that this particular feature will be included in a future revision of the specification. It could just remain a proprietary feature or an implementation-specific optimization.

In this post, Pavel Bucek, a Tyrus team member, discusses how a WebSocket Server Endpoint could be improved when it needs to broadcast a message to its connected remote endpoints. In Tyrus 1.3, a new broadcast() method has been introduced.  It allows you to broadcast a message by re-using the same data frame for all the remote endpoints.  By doing that, the overall performance should be improved.


Discover how organizations are modernizing their application architectures for speed and agility from the growing API economy.  Brought to you in partnership with CA Technologies.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}