Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Socket.IO Cookbook
  • Table Of Contents Toc
Socket.IO Cookbook

Socket.IO Cookbook

By : Tyson Cadenhead
3.3 (6)
Buy this Book
close
close
Socket.IO Cookbook

Socket.IO Cookbook

3.3 (6)
By: Tyson Cadenhead
Buy this Book

Overview of this book

Socket.IO is a JavaScript library that provides you with the ability to implement real-time analytics, binary streaming, instant messaging, and document collaboration. It has two parts: a client-side library that runs in the browser, and a server-side library for node.js. Socket.IO is event-driven and primarily uses the WebSocket protocol that allows us to emit data bi-directionally from the server and the client. Socket.IO This book is a complete resource, covering topics from webSocket security to scaling the server-side of a Socket.IO application and everything in between. This book will provide real-world examples of how secure bi-directional, full-duplex connections that can be created using Socket.IO for different environments. It will also explain how the connection vulnerabilities can be resolved for large numbers of users and huge amounts of data/messages. By the end of the book, you will be a competent Socket.IO developer. With the help of the examples and real-world solutions,you will learn to create fast, scalable, and dynamic real-time apps by creating efficient messaging systems between the server side and the client side using Socket.IO.
Table of Contents (10 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Sections
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. Wiring It Up
chevron up
Icon
1. Wiring It Up
Icon
Introduction
Icon
Creating a Node HTTP server with Socket.IO
Icon
Creating an Express server with Socket.IO
Icon
Using Socket.IO as a cross-browser WebSocket
Icon
Debugging on the client
Icon
Debugging on the server
2
2. Creating Real-Time Dashboards
Icon
2. Creating Real-Time Dashboards
Icon
Introduction
Icon
Loading static data from the server
Icon
Creating a server-side clock
Icon
Loading data from MongoDB
Icon
Real-time analytics
Icon
Handling connection timeouts
3
3. Having Two-Way Conversations
Icon
3. Having Two-Way Conversations
Icon
Introduction
Icon
Creating a simple chat room
Icon
Managing the socket life cycle
Icon
Emitting a private message to another socket
Icon
Sending messages to all the sockets, except for the sender
Icon
Building a multiplayer tic-tac-toe game
4
4. Building a Room with a View
Icon
4. Building a Room with a View
Icon
Introduction
Icon
Creating chat channels with namespaces
Icon
Joining rooms
Icon
Leaving rooms
Icon
Listing rooms the socket is in
Icon
Creating private rooms
Icon
Setting up a default room
5
5. Securing Your Data
Icon
5. Securing Your Data
Icon
Introduction
Icon
Implementing basic authentication
Icon
Performing token-based authentication
Icon
Handling server-side validation
Icon
Locking down the HTTP referrer
Icon
Using secure WebSockets
6
6. Performing a Load Balancing Act
Icon
6. Performing a Load Balancing Act
Icon
Introduction
Icon
Performing load balancing with the Nginx server
Icon
Using the Node.js cluster
Icon
Using Redis to pass events between nodes
Icon
Using Memcached to manage multiple nodes
Icon
Using RabbitMQ to message events across nodes
7
7. Streaming Binary Data
Icon
7. Streaming Binary Data
Icon
Introduction
Icon
Broadcasting an image to other sockets
Icon
Uploading an image to the filesystem
Icon
Uploading an image to Amazon S3
Icon
Streaming audio
Icon
Streaming live video
8
8. Integrating with Mobile Applications
Icon
8. Integrating with Mobile Applications
Icon
Introduction
Icon
Throwing an alert when the socket connects
Icon
Pushing up data from the server
Icon
Responding to tap events from the device
Icon
Doing server-side pagination
Icon
Triggering hot deploys
9
Index
Icon
Index

Debugging on the client

In the earlier versions of Socket.IO, debugging was extremely simple. This was because verbose logging was pushed to the developer console by default. Although this feature was a great way to dig into issues when they occurred, it could also get in the way by logging too much when no debugging was needed.

Now, Socket.IO gives us the ability to toggle certain parts of our logging on and off as needed. In this recipe, we will enable client-side debugging to have a better view of what is happening in our Socket.IO communication.

Getting ready

Starting with version 1.0, Socket.IO doesn't show any logging by default. However, it can easily be turned on. Behind the scenes, it will use an NPM module called debug, which allows logging to navigate to various scopes that can be turned on or off as needed.

How to do it…

To enable debugging on the client side, follow these steps:

  1. On the client side, log settings are persisted through HTML5 localStorage, so you can turn logging on by setting the value of localStorage.debug.
  2. To see all the logging messages, just set the value of debug to an asterisk, as shown in the following code:
    localStorage.debug = '*';
  3. Now that robust logging is turned on, you can open your developer tools and see a rich array of messages that details what is happening under the hood:
    How to do it…

How it works…

The localStorage object in the browser is an object with key/value pairs that is maintained when you refresh the page or leave it entirely. It is useful for persisting data on the client side in modern browsers.

Socket.IO uses the debug NPM module. This views the localStorage key to determine the logging level to be displayed in the browser. The fact that the debugging level is set in localStorage can be very useful because you can set a debugging type anywhere even in production, and it will only log on to your machine. Also, you will be able to refresh the page and see the Socket.IO logging from the initial page load, which can be really handy for debugging events that occur earlier on the page life cycle.

There's more…

Not only can you set the logging to show everything, you can also listen for only certain log types by setting them up in localStorage. For example, if you are only interested in XHR requests, you can ask to only see messages in the engine.io-client:polling-xhr namespace with the following code:

localStorage.debug = 'engine.io-client:polling-xhr';

You can also set multiple log types by separating them with a comma, as shown in the following code:

localStorage.debug = 'engine.io-client:polling, engine.io-client:socket';

See also

The following recipe, Debugging on the server.

CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Socket.IO Cookbook
End of Section 1
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon