Links

Github
Crowdin
Official website

Project Details

Node.js is not a programming language but could be considered as a Java Script programming framework, although in reality the definition of framework is not entirely appropriate, as Node.js could be confused with an environment to create a particular type of applications. To be precise, Node.js is a framework / platform for running JavaScript applications
We therefore say that the most appropriate definition would be that of "platform for the execution of JavaScript applications", as we find written on the home page of the official website; in practice it is a JavaScript run-time, therefore a motor for the execution of JavaScript code.

Introduction

I'm glad that on Node.js I have the chance to start a file from scratch and working to complete its translation: in my previous project instead, there were many files partially translated by other users that just had some scatter word or sentence to render and this sometimes need more time and makes your work unpleasant and confused.
As I have already explained, the whole Italian team is working on Node.js and we are processing all the first folder (API) files, following the descending order as much as possible, to give a better translation.

Contribution Specifications

This is my second report about this new translation project.
Last time I fully completed events.md file, therefore I've chosen a new one: http.md. In this contribution I rendered around 1500 words (21%) of the total 7000 this section is composed of. It's about HTTP different applications of Node.js and their use, specifications and features. I faced mainly several examples of objects called agents that are used to make requests, as new Agent, agent.keepSocketAlive and agent.sockets. I haven't found many repetitions except for the key terms like request, agent, event and connection.

Translation Overview

Introduction to HTTP

To use the HTTP server and client one must require('http').
The HTTP interfaces in Node.js are designed to support many features of the protocol which have been traditionally difficult to use. In particular, large, possibly chunk-encoded, messages. The interface is careful to never buffer entire requests or responses — the user is able to stream data.
HTTP message headers are represented by an object like

HTTP agent

An Agent is responsible for managing connection persistence and reuse for HTTP clients. It maintains a queue of pending requests for a given host and port, reusing a single socket connection for each until the queue is empty, at which time the socket is either destroyed or put into a pool where it is kept to be used again for requests to the same host and port. Whether it is destroyed or pooled depends on the keepAlive option.

agent.destroy

Destroy any sockets that are currently in use by the agent.
It is usually not necessary to do this. However, if using an agent with keepAlive enabled, then it is best to explicitly shut down the agent when it will no longer be used. Otherwise, sockets may hang open for quite a long time before the server terminates them.

Languages

SOURCE LANGUAGE: English

TARGET LANGUAGE: Italian

To check my previous experiences as a translator you can consult my activities on Verdaccio and Joomla projects, selecting my name in the drop-down menu.
You can also view my application for Davinci.

Word count

Words Translated: 1048
Proof of clean words

Proof of Authorship

You can look up Crowdin project on the following link, as well as the summary of my activities.

Credits

I'd like to thank @davinci.witness and @utopian-io for this wonderful project I have the pleasure to work in and another big thank to the italian team, especially to the LM @imcesca and our Node.js expert @robertbira.

(Image by @pab.ink)

The first image is public domain - Source Wikicommon