NodeJS web application listening sock file example_node.js
TCP services written in NodeJS can listen on a sock file (Domain Socket), and its HTTP service can also do the same. Although it doesn't make much sense to connect to a sock file as an HTTP service, so this is just a pure attempt.
TCP service is written like this
var net = require('net');
net.createServer(function (socket) {
socket.on('data', function (data) {
socket.write('received: ' data);
});
}).listen('/tmp/node_tcp.sock');
Connect to the one above '/tmp/node_tcp.sock'
telnet /tmp/node_tcp.sock
Trying /tmp/node_tcp.sock...
Connected to (null).
Escape character is '^]'.
Hello World!
received: Hello World!
To be precise, this article should be the TCP and HTTP monitoring Domain Socket files of NodeJS.
It is still very common for TCP monitoring Domain Socket. For example, sometimes this is done when accessing the local database or cache, such as using '/tmp/mysql.sock' to access the local MySQL service, so there is no need to start it. The TCP port is exposed, security is improved, and performance is also improved.
Now let’s take a look at NodeJS’s HTTP monitoring on Domain Socket, modified from a classic example
var http = require('http');
http.createServer(function (req, res) {
res.writeHead(200, {'Content-Type': 'text/plain'});
res.end('Hello Worldn');
}).listen('/tmp/node_http.sock');
console.log('Server running at /tmp/node_http.sock');
I don’t know yet how to access the above HTTP service in the browser, so use telnet to test
telnet /tmp/node_http.sock
Trying /tmp/node_http.sock...
Connected to (null).
Escape character is '^]'.
GET/HTTP/1.1
HTTP/1.1 200 OK
Content-Type: text/plain
Date: Mon, 26 Jan 2015 04:21:09 GMT
Connection: keep-alive
Transfer-Encoding: chunked
c
Hello World
0
Can correctly handle HTTP requests on '/tmp/node_http.sock'.
Use NodeJS HTTP Client to access
var http = require('http');
var options = {
socketPath: '/tmp/node_http.sock',
Method: 'GET',
path: '/'
};
var req = http.request(options, function(res){
console.log('STATUS: ' res.statusCode);
console.log('HEADERS: ' JSON.stringify(res.headers));
res.on('data', function (chunk){
console.log(chunk.toString());
});
});
req.end();
Execute the above code, if the file name is http_client.js,
node http_client.js
STATUS: 200
HEADERS: {"content-type":"text/plain","date":"Mon, 26 Jan 2015 04:25:49 GMT","connection":"close","transfer-encoding":"chunked" }
Hello World
This article is just for the record. I can’t think of the actual purpose of letting the HTTP service listen on the Domain Socket, and the browser cannot access it.

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The main differences between Node.js and Tomcat are: Runtime: Node.js is based on JavaScript runtime, while Tomcat is a Java Servlet container. I/O model: Node.js uses an asynchronous non-blocking model, while Tomcat is synchronous blocking. Concurrency handling: Node.js handles concurrency through an event loop, while Tomcat uses a thread pool. Application scenarios: Node.js is suitable for real-time, data-intensive and high-concurrency applications, and Tomcat is suitable for traditional Java web applications.

Node.js is a server-side JavaScript runtime, while Vue.js is a client-side JavaScript framework for creating interactive user interfaces. Node.js is used for server-side development, such as back-end service API development and data processing, while Vue.js is used for client-side development, such as single-page applications and responsive user interfaces.

Node.js can be used as a backend framework as it offers features such as high performance, scalability, cross-platform support, rich ecosystem, and ease of development.

To connect to a MySQL database, you need to follow these steps: Install the mysql2 driver. Use mysql2.createConnection() to create a connection object that contains the host address, port, username, password, and database name. Use connection.query() to perform queries. Finally use connection.end() to end the connection.

The following global variables exist in Node.js: Global object: global Core module: process, console, require Runtime environment variables: __dirname, __filename, __line, __column Constants: undefined, null, NaN, Infinity, -Infinity

There are two npm-related files in the Node.js installation directory: npm and npm.cmd. The differences are as follows: different extensions: npm is an executable file, and npm.cmd is a command window shortcut. Windows users: npm.cmd can be used from the command prompt, npm can only be run from the command line. Compatibility: npm.cmd is specific to Windows systems, npm is available cross-platform. Usage recommendations: Windows users use npm.cmd, other operating systems use npm.

The main differences between Node.js and Java are design and features: Event-driven vs. thread-driven: Node.js is event-driven and Java is thread-driven. Single-threaded vs. multi-threaded: Node.js uses a single-threaded event loop, and Java uses a multi-threaded architecture. Runtime environment: Node.js runs on the V8 JavaScript engine, while Java runs on the JVM. Syntax: Node.js uses JavaScript syntax, while Java uses Java syntax. Purpose: Node.js is suitable for I/O-intensive tasks, while Java is suitable for large enterprise applications.

Yes, Node.js is a backend development language. It is used for back-end development, including handling server-side business logic, managing database connections, and providing APIs.
