HTML and CSS Reference
Table 8-3. ( continued )
Buffering and Throttling
Identify where throttling may improve performance.
Identify areas for monitoring.
Hardware Capacity Planning
Identify the memory and CPU requirements for
your WebSocket server.
Identify bandwidth requirements.
Identify the disk requirements of your servers.
Decide if a cloud-based offering would better suit
your application deployment.
Identify the number of concurrent socket
connections your system requirements.
Identify the socket limits for your server.
In this chapter, we examined the steps you can take after you've built your WebSocket
server and application and added the necessary security enhancements to prepare
your application for public consumption. We looked at some of the tasks an application
developer can perform to allow all types of users to access their WebSocket application,
even if the user does not have a WebSocket-enabled browser. We explored ways you can
work with reverse proxy servers and TCP keepalive to maintain WebSocket connections,
use TLS to protect your data (not only from intruders but also from proxies and firewalls),
as well as plan for enterprise-wide deployment.
You've now walked with us through the history of the WebSocket API and Protocol
and examined the benefits of using WebSocket over older HTTP architectures. We've
looked at sample WebSocket traffic and through this examination witnessed the
possibilities of improved performance. We've stepped through using the WebSocket
API and seen how much simpler it is to create full-duplex, bidirectional communication
between a client and server than with older (and more convoluted) AJAX-based
architectures. We explored some of the powerful ways you can use WebSocket to extend
TCP layer application protocols over the Web with widely used standards, like XMPP
and STOMP. With these use cases, we've seen how you can empower standard chat and
messaging protocols with full-duplex, real-time capabilities. We've seen how you can
easily implement desktop sharing using VNC over WebSocket to a plugin-free HTML5
browser client. We've also looked at security and deployment for WebSocket applications,
and considerations you should make before making your applications publicly available.
After reading The Definitive Guide to HTML5 WebSocket , we hope you are not only
armed with a good understanding of WebSocket but are also inspired to take advantage
of this technology to ramp up your existing applications and architectures and develop
new applications that were previously challenging or impossible. It's still in its early days,
and we believe that WebSocket will transform not only web development but also the way
users can interact with information and devices over the Web.