From c0d431d22ee1e2e69338189f9ce5a4b4abc07e6e Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Sat, 10 Jan 2015 04:27:20 +0000 Subject: switch docs + website to olddoc wrongdoc was difficult to maintain because of the tidy-ffi dependency and the HTML5 changes in Darkfish could not be handled well by Tidy. olddoc is superior as it generates leaner HTML which loads faster, requires less scrolling and less processing power to render. Aesthetic comparisons are subjective of course but completely unimportant compared to speed and accessibility. The presence of images and CSS on the old (Darkfish-based) site probably set unreasonable expectations as to my ability and willingness to view such things. No more, the new website is entirely simple HTML which renders well with even the wimpiest browser (hell, olddoc even tries to generate readable raw HTML). --- vs_Unicorn | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'vs_Unicorn') diff --git a/vs_Unicorn b/vs_Unicorn index 67e4250..6f910a7 100644 --- a/vs_Unicorn +++ b/vs_Unicorn @@ -1,11 +1,11 @@ -= \Rainbows! is like Unicorn, but Different... += \Rainbows! is like unicorn, but Different... -While \Rainbows! depends on Unicorn for its process/socket management, +While \Rainbows! depends on unicorn for its process/socket management, HTTP parser and configuration language; \Rainbows! is more ambitious. == Architectural Diagrams -=== Unicorn uses a 1:1 mapping of processes to clients +=== unicorn uses a 1:1 mapping of processes to clients unicorn master \_ unicorn worker[0] @@ -52,16 +52,16 @@ In both cases, workers share common listen sockets with the master and pull connections off the listen queue only if the worker has resources available. -== Differences from Unicorn +== Differences from unicorn -* log rotation is handled immediately in \Rainbows! whereas Unicorn has +* log rotation is handled immediately in \Rainbows! whereas unicorn has the luxury of delaying it until the current request is finished processing to prevent log entries for one request to be split across files. * load balancing between workers is imperfect, certain worker processes may be servicing more requests than others so it is important to not - set +worker_connections+ too high. Unicorn worker processes can never + set +worker_connections+ too high. unicorn worker processes can never be servicing more than one request at once. * speculative, non-blocking accept() is not used, this is to help @@ -72,10 +72,10 @@ available. * Less heavily-tested and inherently more complex. -== Similarities with Unicorn +== Similarities with unicorn While some similarities are obvious (we depend on and subclass off -Unicorn code), some things are not: +unicorn code), some things are not: * Does not attempt to accept() connections when pre-configured limits are hit (+worker_connections+). This will first help balance load -- cgit v1.2.3-24-ge0c7