Lessons: 15Length: 2.9 hours
- Overview
- Transcript
2.12 Spawning
As we now know, Node (like the browser) runs in a single thread. This means that, if we are running some code that is very processor intensive, then it can delay and slow down other executing code. Sometimes, it can be necessary to spawn additional processes to do some intensive work for us. For this lesson, we are going to spawn processes to collect Twitter data for some different topics.
1.Introduction
1.1Hello Node.js07:31
1.1
Hello Node.js
07:31
1.2Installation07:28
1.2
Installation
07:28
2.Node.js
2.1The File System14:58
2.1
The File System
14:58
2.2My First Web Server13:34
2.2
My First Web Server
13:34
2.3Node Package Manager07:29
2.3
Node Package Manager
07:29
2.4My Second Web Server with Express10:14
2.4
My Second Web Server with Express
10:14
2.5Connecting to the Outside World11:40
2.5
Connecting to the Outside World
11:40
2.6Creating a Module08:38
2.6
Creating a Module
08:38
2.7Publishing to NPM06:46
2.7
Publishing to NPM
06:46
2.8MongoDB21:43
2.8
MongoDB
21:43
2.9Twitter Streaming API12:22
2.9
Twitter Streaming API
12:22
2.10My Third Web Server with Socket.IO15:54
2.10
My Third Web Server with Socket.IO
15:54
2.11Nodester16:54
2.11
Nodester
16:54
2.12Spawning13:58
2.12
Spawning
13:58
3.Conclusion
3.1Tips and Troubleshooting07:10
3.1
Tips and Troubleshooting
07:10
