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 third report about Node.js translation and it regards in particular the second session on http.md file (you can find the first part here).
Today I have reached the 50% of this specific file which is focused on Node.js different HTTP applications: it started analyzing some event, then it handled various request types and their use and finally a couple of server functions.
I had to process more than 2000 words to get 1000 clean words.

Translation Overview

Event: 'clientError'

If a client connection emits an 'error' event, it will be forwarded here. Listener of this event is responsible for closing/destroying the underlying socket. For example, one may wish to more gracefully close the socket with a custom HTTP response instead of abruptly severing the connection.
Default behavior is to close the socket with an HTTP '400 Bad Request' response if possible, otherwise the socket is immediately destroyed.

request.flushHeaders()

Flush the request headers.
For efficiency reasons, Node.js normally buffers the request headers until request.end() is called or the first chunk of request data is written. It then tries to pack the request headers and data into a single TCP packet.
That's usually desired (it saves a TCP round-trip), but not when the first data is not sent until possibly much later. request.flushHeaders() bypasses the optimization and kickstarts the request.
request.getHeader(name)

server.setTimeout([msecs][, callback])

Sets the timeout value for sockets, and emits a 'timeout' event on the Server object, passing the socket as an argument, if a timeout occurs.
If there is a 'timeout' event listener on the Server object, then it will be called with the timed-out socket as an argument.

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: 1044

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