938 karma · joined May 16, 2012
https://www.twitter.com/antcatel http://www.github.com/paraboul
e-mail: [username] at gmail
That said, using a driver in another thread leads to various complexities that can be avoided when running in the same application (javascript/v8) thread/event loop.
Previous HN thread : https://news.ycombinator.com/item?id=6314961
An excellent book that can teach you the basics (from trigonometry to advanced linear algebra) is "3D Math Primer for Graphics and Game Development".
One usually want to reimplement a reliable protocol (e.g. similar to TCP) on top of UDP when dealing with peer-to-peer capabilities.
Indeed, NAT traversal is easier to implement and more reliable when dealing with UDP techniques (e.g. UDP hole punching).
nginx does a lot of optimization at many level that ab can't figure out.
In short, it only profiles the speed of the HTTP parser and certainly not the network stack.
There are a lot of things that a HTTP server does in order to keep the connections stack "steady" : Disabling the Nagle algorithm at the right moment, gracefully handling failure, managing slow clients the right way, ...
FWIW, Tsung is an awesome benchmarking tool written in erlang : http://tsung.erlang-projects.org/
http://vosdroits.service-public.fr/particuliers/F19708.xhtml
I think there is a confusion between "leaving your job on your own" and leaving in a consensual way with your employer.
Most of the time, when you decide to leave, you make a departure plan with your employer. If your employer agree with your decision, you generally leave after 3 month or so (depending on the terms of the contract).
You can then ask for you unemployment benefits.
It tries to copy a buffer of 1024 byte (max) into a buffer of 512 bytes (by executing a request with an URL longer than 512 bytes).
It also runs 15 children process and use blocking socket, meaning that it's easily "DoS'able".
The overall code seems very "unsecure" and poorly designed.
Otherwise, it would have had to write a TCP stack, drivers, ...
A general rule when designing a network protocol : do your best to make the client-side closes the connection when possible.
I mean, I don't invent anything :
https://bugzilla.mozilla.org/show_bug.cgi?id=979923
https://www.google.com/search?sitesearch=bugzilla.mozilla.or...
edit: since I get downvoted, source : https://www.google.com/#q=fat+arrow+es6
I think there is a good balance between using third party library (possibly untrusted) and plain C. Kind of an analogy to centralized network vs decentralized.
A good exemple is Daniel J. Bernstein. The man doesn't even trust the libc and wrote its own layer for all of his software (djbdns, qmail, ...). (source : http://cr.yp.to/qmail/guarantee.html #7)
That is : One can easily rewrite a TCP-like on top of UDP.