There are many methods to write internet servers but they can - fundamentally be divided into two camps: evented and threaded; non-blocking - and blocking. A blocking server accepts a connection and launches a new - thread to handle the connection. Because the concurrency is handled by - the thread scheduler, a blocking server can make function calls which - preform full network requests. +
There are many methods to write internet servers but they can +fundamentally be divided into two camps: evented and threaded; non-blocking +and blocking. A blocking server accepts a connection and launches a new +thread to handle the connection. Because the concurrency is handled by +the thread scheduler, a blocking server can make function calls which +preform full network requests.
var response = db.execute("SELECT * FROM table");
// do something
- An evented server manages its concurrency itself. All connections - are handled in a single thread and callbacks are executed on certain - events: "socket 23 is has data to read", "socket 65's write buffer is - empty". An evented server executes small bits of code but never - blocks the process. In the evented world callbacks are used - instead of functions +
An evented server manages its concurrency itself. All connections +are handled in a single thread and callbacks are executed on certain +events: "socket 23 is has data to read", "socket 65's write buffer is +empty". An evented server executes small bits of code but never +blocks the process. In the evented world callbacks are used +instead of functions
db.execute("SELECT * FROM table", function (response) {
-// do something
+ // do something
});
-
l1 cache ~ 3
l2 cache ~ 14
@@ -169,9 +179,10 @@ l2 cache ~ 14
disk ~ 41000000
network ~ 240000000
- purely evented interfaces rule out a lot of stupidity + +
Javascript is without I/O. In the browser the DOM provides I/O, @@ -200,7 +211,6 @@ l2 cache ~ 14 systems tend to be written in C and portable web-level systems are written in Javascript.