Book Image

Node Cookbook

By : David Mark Clements
Book Image

Node Cookbook

By: David Mark Clements

Overview of this book

The principles of asynchronous event-driven programming are perfect for today's web, where efficient real-time applications and scalability are at the forefront. Server-side JavaScript has been here since the 90's but Node got it right. With a thriving community and interest from Internet giants, it could be the PHP of tomorrow. "Node Cookbook" shows you how to transfer your JavaScript skills to server side programming. With simple examples and supporting code, "Node Cookbook" talks you through various server side scenarios often saving you time, effort, and trouble by demonstrating best practices and showing you how to avoid security faux pas. Beginning with making your own web server, the practical recipes in this cookbook are designed to smoothly progress you to making full web applications, command line applications, and Node modules. Node Cookbook takes you through interfacing with various database backends such as MySQL, MongoDB and Redis, working with web sockets, and interfacing with network protocols, such as SMTP. Additionally, there are recipes on correctly performing heavy computations, security implementations, writing, your own Node modules and different ways to take your apps live.
Table of Contents (16 chapters)
Node Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface

Dynamic routing


In the very first recipe of this cookbook, Setting up a router, we explored various ways to set up routing in Node. Express provides a far superior and very powerful routing interface which we'll explore in this recipe.

Getting ready

We'll be working with our nca folder.

How to do it...

Let's say we want to add a page for a fictional character by the name of Mr Page. We'll name the route page, so in the routes section of app.js we add the following code:

app.get('/page', function (req, res) {
res.send('Hello I am Mr Page');
});

We can also define flexible routes, and grab the requested route using req.params, like so:

app.get('/:page', function (req, res) {
res.send('Welcome to the ' + req.params.page + ' page');
});

It's okay to throw our callbacks directly into app.get while developing, but in the interest of a clutter-free app.js let's take our callbacks and load them from routes/index.js as follows:

exports.index = function(req, res){
res.render('index', { title: 'Express...