Employing Streams | Node Cookbook: Second Edition

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents

Node Cookbook: Second Edition

By : David Mark Clements

4.3 (7)

Node Cookbook: Second Edition

4.3 (7)

By: David Mark Clements

Overview of this book

In Node Cookbook Second Edition, each chapter focuses on a different aspect of working with Node. Following a Cookbook structure, the recipes are written in an easy-to-understand language. Readers will find it easier to grasp even the complex recipes which are backed by lots of illustrations, tips, and hints. If you have some knowledge of JavaScript and want to build fast, efficient, scalable client-server solutions, then Node Cookbook Second Edition is for you. Knowledge of Node will be an advantage but is not required. Experienced users of Node will be able to improve their skills.

Node Cookbook Second Edition

Node Cookbook Second Edition

Credits

Credits

About the Author

About the Author

About the Reviewers

About the Reviewers

www.PacktPub.com

www.PacktPub.com

Preface

Preface

Free Chapter

Making a Web Server

Making a Web Server

Introduction

Setting up a router

Serving static files

Caching content in memory for immediate delivery

Optimizing performance with streaming

Securing against filesystem hacking exploits

Exploring the HTTP Object

Exploring the HTTP Object

Introduction

Processing POST data

Handling file uploads

Using Node as an HTTP client

Implementing download throttling

Working with Data Serialization

Working with Data Serialization

Introduction

Converting an object to JSON and back

Converting an object to XML and back

Browser-server transmission via AJAX

Working with real data – fetching trending tweets

Interfacing with Databases

Interfacing with Databases

Introduction

Writing to a CSV file

Connecting and sending SQL to a MySQL server

Storing and retrieving data with MongoDB

Storing data to CouchDB with Cradle

Retrieving data from CouchDB with Cradle

Accessing the CouchDB changes stream with Cradle

Storing and retrieving data with Redis

Implementing PubSub with Redis

Employing Streams

Employing Streams

Introduction

Consuming streams

Playing with pipes

Making stream interfaces

Streaming across Node processes

Going Real Time

Going Real Time

Introduction

Creating a WebSocket server

Cross-browser real-time logic with Socket.IO

Remote Procedure Calls with Socket.IO

Creating a real-time widget

Accelerating Development with Express

Accelerating Development with Express

Introduction

Generating Express scaffolding

Managing server tier environments

Implementing dynamic routing

Templating in Express

CSS preprocessors with Express

Initializing and using a session

Making an Express web app

Implementing Security, Encryption, and Authentication

Implementing Security, Encryption, and Authentication

Introduction

Implementing Basic Authentication

Hashing passwords

Implementing Digest Authentication

Setting up an HTTPS web server

Preventing cross-site request forgery

Integrating Network Paradigms

Integrating Network Paradigms

Introduction

Sending an e-mail

Sending an SMS

Communicating with TCP

Creating an SMTP server

Implementing a virtual hosting paradigm

Writing Your Own Node Modules

Writing Your Own Node Modules

Introduction

Creating a test-driven module specification

Writing a functional module mock-up

Refactoring with prototypical inheritance

Extending a module's API

Deploying a module to npm

Taking It Live

Taking It Live

Introduction

Deploying an app to a server environment

Automatic crash recovery

Continuous deployment

Hosting with a Platform as a Service provider

Index

Index

Consuming streams

As of Node v0.10.x, every readable stream has a read method that can be used to access data that's loaded into our read stream. Prior to Node v0.10.x, chunks of data were captured by listening to a data event; we can still do this when it is suitable (see the There's More… section) but this depends on the use case; therefore using the read method instead can be cleaner.

In this recipe, we're going to receive a stream from the Couch database that backs the npm registry and simply log out everything we get.

Getting ready

All we need to do is create a file named npm_stream_receiver.js.

How to do it…

We're going use the response object returned from an http.get call as our readable stream and set up some initial variables, so we'll require the http module as shown in the following code:

var http = require('http'), feed = 'http://isaacs.iriscouch.com/registry/_changes?feed=continuous', ready = false;

We'll pass the feed variable to http.get.

The ready variable is being used to introduce...

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

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.

Node Cookbook: Second Edition

Search

Your notes and bookmarks