Difference between revisions of "Node"
(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 | + | |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. |
| + | |Homepage URL=http://nodejs.org/ | ||
|User level=intermediate | |User level=intermediate | ||
| − | |||
| − | |||
| − | |||
| − | |||
|Computer languages=JavaScript | |Computer languages=JavaScript | ||
|Documentation note=http://nodejs.org/api.html | |Documentation note=http://nodejs.org/api.html | ||
| − | |||
| − | |||
|IRC general=irc://irc.freenode.net/node.js | |IRC general=irc://irc.freenode.net/node.js | ||
| − | |||
|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 | ||
| − | | | + | |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 | ||
| − | | | + | |Status= |
| − | | | + | |Is GNU=No |
| − | | | + | |License verified date=2010-05-05 |
| − | | | + | }} |
| + | {{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 | ||
| − | |||
}} | }} | ||
{{Person | {{Person | ||
| + | |Real name=See Node AUTHOR file | ||
|Role=Maintainer | |Role=Maintainer | ||
| − | |||
| − | |||
|Resource URL= | |Resource URL= | ||
}} | }} | ||
| Line 49: | Line 57: | ||
|Use=software-development | |Use=software-development | ||
}} | }} | ||
| − | {{ | + | {{Featured}} |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | }} | ||
Revision as of 13:14, 23 March 2013
Node
http://nodejs.org/
evented I/O for V8 javascript.
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 general channel- irc://irc.freenode.net/node.js
Download
http://nodejs.org/dist/latest/
version 0.10.1
(developmental)
released on 21 March 2013
User level
Intermediate
Categories
Related Projects
Licensing
License
Verified by
Verified on
Notes
Leaders and contributors
| Contact(s) | Role |
|---|---|
| See Node AUTHOR file | Maintainer |
Resources and communication
| Audience | Resource type | URI |
|---|---|---|
| Developer | Forum | http://groups.google.com/group/nodejs |
| Debian (Ref) | https://tracker.debian.org/pkg/node | |
| Savannah (Ref) | https://savannah.nongnu.org/projects/node | |
| Python (Ref) | https://pypi.org/project/node | |
| Ruby (Ref) | https://rubygems.org/gems/node |
Software prerequisites
This entry (in part or in whole) was last reviewed on 13 April 2018.
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.