Socket.IO is an excellent library for real-time messaging between the client side and the server side. Whether you want to create a chat room in your browser, reload your hybrid mobile application, or push fresh data to an internal dashboard, this book will show you how to do it.
Chapter 1, Wiring It Up, provides a quick introduction to Socket.IO. It tells you how to get up and running with a Node server. This chapter concludes with debugging tips for the server and the client.
Chapter 2, Creating Real-Time Dashboards, talks about how to stream data from the server to the client. It covers how to emit MongoDB data and how to handle Socket.IO connection timeouts.
Chapter 3, Having Two-Way Conversations, provides several recipes on how to build a two-way communication. From the quintessential chat room example to a fun recipe on how to create a real-time tic-tac-toe game, it includes several other topics.
Chapter 4, Building a Room with a View, explores views and namespaces and how they can be used to target your events to specific consumers.
Chapter 5, Securing Your Data, takes a look at how to secure the Socket.IO communication with various forms of authentication, including how to lock down the HTTP referrer and how to use secure web sockets.
Chapter 6, Performing a Load Balancing Act, covers various techniques for load-balancing Socket.IO, focusing on technologies such as Redis, Memcached, and RabbitMQ.
Chapter 7, Streaming Binary Data, explores topics ranging from emitting images as data to streaming video and audio.
Chapter 8, Integrating With Mobile Applications, talks about various techniques for using Socket.IO in mobile applications. It also provides a recipe for how to trigger hot deploys from Socket.IO.
This book was written using a Macbook Air running Node. However, Node and Socket.IO can be run on a Windows or Linux machine as well.
All the software used in this book is free and open source. You will definitely need to be running Node for most of the recipes. There are also some sections that cover MongoDB, Redis, Memcached, and RabbitMQ.
If you have some knowledge of JavaScript and Node.js and want to create awe-inspiring application experiences with real-time communication, then this book is for you. Developers with knowledge of other languages should also be able to easily follow along.
In this book, you will find several headings that appear frequently (Getting ready, How to do it..., How it works..., There's more..., and See also).
To give clear instructions on how to complete a recipe, we use these sections as follows:
This section tells you what to expect in the recipe and describes how to set up any software or any preliminary settings required for the recipe.
This section usually consists of a detailed explanation of what happened in the previous section.
This section consists of additional information about the recipe in order to make the reader more knowledgeable about the recipe.
In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.
Code words in text, folder names, filenames, file extensions, pathnames, dummy URLs, and user input are shown as follows: "We can include Socket.IO by using the require('socket.io')
statement."
A block of code is set as follows:
var io = require('socket.io'); io.on('connection', function (socket) { socket.emit('connected'); });
New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "For this example we will use Redis to propagate our state across servers."
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or disliked. Reader feedback is important for us as it helps us develop titles that you will really get the most out of.
To send us general feedback, simply e-mail <[email protected]>
, and mention the book's title in the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide at www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
You can download the example code files from your account at http://www.packtpub.com for all the Packt Publishing books you have purchased. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.
We also provide you with a PDF file that has color images of the screenshots/diagrams used in this book. The color images will help you better understand the changes in the output. You can download this file from: https://www.packtpub.com/sites/default/files/downloads/0865OS_ColorImages.pdf.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you could report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the Errata Submission Form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded to our website or added to any list of existing errata under the Errata section of that title.
To view the previously submitted errata, go to https://www.packtpub.com/books/content/support and enter the name of the book in the search field. The required information will appear under the Errata section.
Piracy of copyrighted material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works in any form on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]>
with a link to the suspected pirated material.
We appreciate your help in protecting our authors and our ability to bring you valuable content.
If you have a problem with any aspect of this book, you can contact us at <[email protected]>
, and we will do our best to address the problem.