Free Software Foundation!

Join now

Difference between revisions of "Node"

From Free Software Directory
Jump to: navigation,
(Created page with "{{Entry |Name=Node |Short description=evented I/O for V8 javascript. |Full description=Evented I/O for V8 javascript. Node's goal is to provide an easy way to build scalable netw...")
 
(update versions, download)
 
Line 2: Line 2:
 
|Name=Node
 
|Name=Node
 
|Short description=evented I/O for V8 javascript.
 
|Short description=evented I/O for V8 javascript.
|Full description=Evented I/O for V8 javascript. Node's goal is to provide an easy way to build scalable network programs. This is in contrast to today's more common concurrency model where OS threads are employed. Thread-based networking is relatively inefficient and very difficult to use. Node will show much better memory efficiency under high-loads than systems which allocate 2mb thread stacks for each connection. Furthermore, users of Node are free from worries of dead-locking the process—there are no locks. Almost no function in Node directly performs I/O, so the process never blocks. Because nothing blocks, less-than-expert programmers are able to develop fast systems. Node is similar in design to and influenced by systems like Ruby's Event Machine or Python's Twisted. Node takes the event model a bit further—it presents the event loop as a language construct instead of as a library. In other systems there is always a blocking call to start the event-loop. Typically one defines behavior through callbacks at the beginning of a script and at the end starts a server through a blocking call like EventMachine::run(). In Node there is no such start-the-event-loop call. Node simply enters the event loop after executing the input script. Node exits the event loop when there are no more callbacks to perform.
+
|Full description=Evented I/O for V8 javascript. Node's goal is to provide an easy way to build scalable network programs. This is in contrast to today's more common concurrency model where OS threads are employed. Thread-based networking is relatively inefficient and very difficult to use. Node will show much better memory efficiency under high-loads than systems which allocate 2mb thread stacks for each connection. Furthermore, users of Node are free from worries of dead-locking the process, there are no locks. Almost no function in Node directly performs I/O, so the process never blocks. Because nothing blocks, less-than-expert programmers are able to develop fast systems. Node is similar in design to and influenced by systems like Ruby's Event Machine or Python's Twisted. Node takes the event model a bit further: it presents the event loop as a language construct instead of as a library. In other systems there is always a blocking call to start the event-loop. Typically one defines behavior through callbacks at the beginning of a script and at the end starts a server through a blocking call like EventMachine run(). In Node there is no such start-the-event-loop call. Node simply enters the event loop after executing the input script. Node exits the event loop when there are no more callbacks to perform.
|User level=intermediate
+
|Status=Live
+
|Component programs=
+
 
|Homepage URL=http://nodejs.org/
 
|Homepage URL=http://nodejs.org/
|VCS checkout command=
+
|User level=intermediate
 
|Computer languages=JavaScript
 
|Computer languages=JavaScript
 
|Documentation note=http://nodejs.org/api.html
 
|Documentation note=http://nodejs.org/api.html
|Paid support=
 
|IRC help=
 
 
|IRC general=irc://irc.freenode.net/node.js
 
|IRC general=irc://irc.freenode.net/node.js
|IRC development=
 
 
|Related projects=NodeRed
 
|Related projects=NodeRed
 
|Keywords=Web,Web server,language,event,javascript,I/O,Google
 
|Keywords=Web,Web server,language,event,javascript,I/O,Google
|Is GNU=n
+
|Version identifier=0.10.1
 +
|Version date=2013/03/21
 +
|Version status=developmental
 +
|Version download=http://nodejs.org/dist/latest/
 
|Last review by=Kelly Hopkins
 
|Last review by=Kelly Hopkins
 
|Last review date=2010-05-05
 
|Last review date=2010-05-05
 
|Submitted by=Database conversion
 
|Submitted by=Database conversion
 
|Submitted date=2011-04-01
 
|Submitted date=2011-04-01
|Version identifier=0.1.93
+
|Status=
|Version date=2010-04-29
+
|Is GNU=No
|Version status=stable
+
|License verified date=2010-05-05
|Version download=http://nodejs.org/dist/node-v0.1.93.tar.gz
+
}}
 +
{{Project license
 +
|License=BSD_3Clause
 +
|License verified by=Kelly Hopkins
 +
|License verified date=2010-05-05
 +
}}
 +
{{Project license
 +
|License=BSD_2Clause
 +
|License verified by=Kelly Hopkins
 +
|License verified date=2010-05-05
 +
}}
 +
{{Project license
 +
|License=Expat
 +
|License verified by=Kelly Hopkins
 
|License verified date=2010-05-05
 
|License verified date=2010-05-05
|Version comment=
 
 
}}
 
}}
 
{{Person
 
{{Person
|Role=Maintainer
 
 
|Real name=See Node AUTHOR file
 
|Real name=See Node AUTHOR file
|Email=
+
|Role=Maintainer
 
|Resource URL=
 
|Resource URL=
 
}}
 
}}
Line 49: Line 57:
 
|Use=software-development
 
|Use=software-development
 
}}
 
}}
{{Project license
+
{{Featured}}
|License=BSD_3Clause
+
|License verified by=Kelly Hopkins
+
|License verified date=2010-05-05
+
}}
+
{{Project license
+
|License=BSD_2Clause
+
|License verified by=Kelly Hopkins
+
|License verified date=2010-05-05
+
}}
+
{{Project license
+
|License=Expat
+
|License verified by=Kelly Hopkins
+
|License verified date=2010-05-05
+
}}
+

Latest revision as of 14:14, 23 March 2013

[edit]

Node

http://nodejs.org/
Evented I/O for V8 javascript. Node's goal is to provide an easy way to build scalable network programs. This is in contrast to today's more common concurrency model where OS threads are employed. Thread-based networking is relatively inefficient and very difficult to use. Node will show much better memory efficiency under high-loads than systems which allocate 2mb thread stacks for each connection. Furthermore, users of Node are free from worries of dead-locking the process, there are no locks. Almost no function in Node directly performs I/O, so the process never blocks. Because nothing blocks, less-than-expert programmers are able to develop fast systems. Node is similar in design to and influenced by systems like Ruby's Event Machine or Python's Twisted. Node takes the event model a bit further: it presents the event loop as a language construct instead of as a library. In other systems there is always a blocking call to start the event-loop. Typically one defines behavior through callbacks at the beginning of a script and at the end starts a server through a blocking call like EventMachine run(). In Node there is no such start-the-event-loop call. Node simply enters the event loop after executing the input script. Node exits the event loop when there are no more callbacks to perform.

Documentation

http://nodejs.org/api.html

"IRC irc://irc.freenode.net/node.js " IRC general channel
irc://irc.freenode.net/node.js


Download

Download External-link-icon.png version 0.10.1 (developmental)
released on 21 March 2013

Categories

Related Projects




Licensing

LicenseVerified byVerified onNotes
BSD 3ClauseKelly Hopkins5 May 2010
BSD 2ClauseKelly Hopkins5 May 2010
ExpatKelly Hopkins5 May 2010



Leaders and contributors

Contact(s)Role
See Node AUTHOR fileMaintainer


Resources and communication

Audience Resource type URI
Developer Forum http://groups.google.com/group/nodejs
Support Mailing List Subscribe http://groups.google.com/group/nodejs


Software prerequisites

This entry (in part or in whole) was last reviewed on 5 May 2010.



Entry





























Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.

The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.


Personal tools
Namespaces

Variants
Actions
Navigation
Contribute