Timeline for How can NodeJS be "non-blocking"?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 4, 2016 at 18:20 | comment | added | Erik Reppen | Detail that might help. Node leverages the V8 JS engine. One of V8's best features is ease of binding C/C++ processes to JS calls. JavaScript functions are blocking but all a function does is call something under the hood that doesn't block. Then another JS function responds when that process is done. JS functions blocking each other means you'll never have two things trying to do something like schedule a write to the same file location at the same time which is where I assume multi-threaded needs to be managed. It's always clear which request came first for the purpose of queuing things. | |
| Jun 19, 2013 at 12:22 | vote | accept | Anonymous | ||
| Jun 19, 2013 at 10:45 | comment | added | Florian Margaine |
There is the net package when http is not available.
|
|
| Jun 19, 2013 at 10:39 | review | First posts | |||
| Jun 19, 2013 at 10:48 | |||||
| Jun 19, 2013 at 10:23 | history | answered | ckknight | CC BY-SA 3.0 |