《Node.js实战指南》：快速掌握服务器端JavaScript开发

nodejs

需积分: 42 102 浏览量更新于2024-07-17 收藏 5.39MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

East of the mountain range, we find the client-side programs. These include

GUI tools of all stripes, consumer applications, mobile apps, and web apps.

Client-side programs interact directly with human beings, often by waiting

patiently for their input.

West of the mountains are the server-side programs. This vast expanse is

Node.js territory.

Deep within the server-side region lies the Web—that old guard of HTTP, Ajax,

REST, and JSON. The websites, apps, and APIs that consume so much of

our collective mental energy live here.

Because we spend so much time thinking about the Web, we overemphasize

Node’s use in developing web applications. People ask, “How is Node better

for making web apps?” or, “How can I make a REST service with Node?”

These are good questions, but they miss the point. Node is great for a wider

range of things, and this book explores that larger world.

Node’s Niche

Since JavaScript’s first appearance in 1995, it has been solving problems all

along the front-end/back-end spectrum. The following figure shows this

spectrum and where Node.js fits within it.

Figure 2—Node’s place in the JavaScript spectrum

In the web browser on the right, much of the scripting involves waiting for

user interaction. Click here, drag that, choose a file, etc. JavaScript has been

extraordinarily successful in this space.

Chapter 1. Getting Started • 2

report erratum • discuss

Prepared exclusively for jabez zhang

As long as there’s something left to do, Node’s event loop will keep spinning.

Whenever an event occurs, Node invokes any callbacks (event handlers) that

are listening for that event.

As a Node developer, your job is to create the callback functions that get

executed in response to events. Any number of callbacks can respond to any

event, but only one callback function will ever be executing at any time.

Everything else your program might do—like waiting for data from a file or

an incoming HTTP request—is handled by Node, in parallel, behind the scenes.

Your application code will never be executed at the same time as anything

else. It will always have the full attention of Node’s JavaScript engine while

it’s running.

Single-Threaded and Highly Parallel

Other systems try to gain parallelism by running lots of code at the same

time, typically by spawning many threads. But not Node.js. For JavaScript,

Node is a single-threaded environment. At most, only one line of your code

will ever be executing at any time.

Node gets away with this by doing most I/O tasks using nonblocking

techniques. Rather than waiting line-by-line for an operation to finish, you

create a callback function that will be invoked when the operation eventually

succeeds or fails.

Your code should do what it needs to do, then quickly hand control back over

to the event loop so Node can work on something else. We’ll develop practical

examples of this throughout the book, starting in Chapter 2, Wrangling the

File System, on page 9.

If it seems strange to you that Node achieves parallelism by running only one

piece of code at a time, that’s because it is. It’s an example of something I call

a backwardism.

Backwardisms in Node.js

A backwardism is a concept that’s so bizarre that at first it seems completely

backwards. You’ve probably experienced many backwardisms while learning

to program, whether you noticed them or not.

Take the concept of a variable. In algebra it’s common to see equations like

“

7x + 3 = 24

.” Here,

is called a variable; it has exactly one value, and your job

is to figure out what that value is.

Chapter 1. Getting Started • 4

report erratum • discuss

Prepared exclusively for jabez zhang

Then when you start learning how to program, you quickly run into statements

like “

x = x + 7

.” Now

is still called a variable, but it can have any value that

you assign to it. It can even have different values at different times.

From algebra’s perspective, this is a backwardism. The equation “

x = x + 7

”

makes no sense at all. The notion of a variable in programming is not just a

little different—it’s 100 percent backwards. But once you understand the

concept of assignment, the programming variable makes perfect sense.

So it is with Node’s single-threaded event loop. From a multithreaded perspec-

tive, running just one piece of code at a time seems silly. But once you

understand event-driven programming—with nonblocking APIs—it becomes

clear.

Programming is chock-full of backwardisms like these, and Node.js is no

exception. Starting out, you’ll frequently run into code that looks like it should

work one way, but it actually does something quite different.

That’s OK! With this book, you’ll learn Node by making compact programs

that interact in useful ways. As we run into more of Node’s backwardisms,

we’ll dive in and explore them.

Aspects of Node.js Development

Node.js is a surprisingly big subject, so let’s break it down into different

aspects. There are many aspects of Node.js development we might talk about,

ranging from basic JavaScript syntax to revision control. This book focuses

on five in particular:

• Practical programming

• Architecture and core

• Patterns

• JavaScriptisms

• Supporting code

Let’s explore each of these briefly.

Practical Programming

Practical programming is all about producing real code that does something

useful. Interacting with a file system, establishing socket connections, or

serving web applications are all examples of practical programming.

Each of the remaining chapters of this book focuses on one particular practical

domain. Through code examples specific to each domain, you’ll learn Node’s

architecture, patterns, JavaScriptisms, and supporting code.

report erratum • discuss

Aspects of Node.js Development • 5

Prepared exclusively for jabez zhang

Architecture and Core

Understanding Node’s architecture will help you to harness its features while

avoiding performance-crushing pitfalls. For example, Node uses an event loop

written in C for scheduling work. But it executes application code in a Java-

Script environment. How information is shuttled between these layers is the

kind of impactful architectural detail you’ll learn.

Patterns

Like any successful codebase with a healthy ecosystem, Node.js has a number

of repeating patterns. Some of these patterns are baked into the core while

others mostly appear in third-party libraries. Examples include the use of

callbacks, error-handling techniques, and classes like

EventEmitter

and

Stream

which are used liberally for event dispatching.

As we progress through different practical programming domains, we’ll natu-

rally encounter these and other patterns. When we do, you’ll discover why

they’re useful and how to use them effectively.

JavaScriptisms

JavaScript is the language of Node programs, so you’ll be seeing quite a lot

of it. The code examples in this book make use of the latest available Java-

Script features. Some of these features may be unfamiliar to you, even if

you’ve done JavaScript development before.

JavaScriptisms discussed in this book include things like the nature of

functions and object inheritance. ECMAScript Harmony—the code name for

the next version of the JavaScript spec—packs some new features we’ll use,

too.

Supporting Code

Code does not live in isolation; it takes a village to support any individual

program. Supporting code covers lots of things, from unit testing to perfor-

mance benchmarks to deployment scripts. We’ll use supporting code

throughout the book to make our programs more robust, more scalable, and

more manageable.

With these five aspects, you’ll be able to develop applications that make the

most use out of the platform while using idiomatic Node.js style. The example

applications you’ll develop in this book are functional and small, and aim to

clearly demonstrate the five aspects. But to use them, you’ll need to get Node.js

installed first.

Chapter 1. Getting Started • 6

report erratum • discuss

Prepared exclusively for jabez zhang

剩余142页未读，继续阅读

house.zhang

粉丝: 35
资源: 8

《Node.js实战指南》：快速掌握服务器端JavaScript开发

HTML转WORD WORD转PDF

node-msoffice-pdf:将Word，Excel和PowerPoint导出为PDF的模块。 需要Windows和已安装的Office 2013

convert-word-to-pdf:python将word转换为pdf

深入浅出nodejs.pdf 朴灵著

vue 预览pdf文件

nodejs将pdf文件转为word文件

nodejs pdf文件预览加水印

nodejs中文文档下载

nodejs pdf模块

使用nodejs 将uvz转换为pdf

nodejs入门 pdf

使用nodejs实现图片合成pdf

用nodejs，将目录及子目录下，以pdf为后缀的文件都列举出来

nodejs开发指南pdf

nodejs实现将png图片转换成pdf

D:\workspace\shidihoutai\ruoyi-ui\src\components\pdf\index.vue` does not match the corresponding path on disk `Pdf`.

nodejs如何将本地dwg格式的文件转化为二进制流

用Marpit Markdow制作一个幻灯片

nodejs换镜像源

写nodejs代码，将目录及子目录的pdf文件列举出来

最新资源

node-msoffice-pdf:将Word，Excel和PowerPoint导出为PDF的模块。需要Windows和已安装的Office 2013