DEPLOY FAQ HACKING LICENSE NEWS README SIGNALS Sandbox Static_Files Summary TUNING Test_Suite rainbows_1 vs_Unicorn
Rainbows ActorSpawn AppPool Base Configurator Coolio CoolioThreadPool CoolioThreadSpawn DevFdResponse Epoll EventMachine FiberPool FiberSpawn MaxBody NeverBlock Rev RevFiberSpawn RevThreadPool RevThreadSpawn Revactor Sendfile ServerToken StreamResponseEpoll ThreadPool ThreadSpawn ThreadTimeout WriterThreadPool WriterThreadSpawn XEpoll XEpollThreadPool XEpollThreadSpawn

module Rainbows::StreamResponseEpoll

Like Unicorn itself, this concurrency model is only intended for use behind nginx and completely unsupported otherwise. Even further from Unicorn, this isn't even a good idea with normal LAN clients, only nginx!

It does NOT require a thread-safe Rack application at any point, but allows streaming data asynchronously via nginx (using the "X-Accel-Buffering: no" header to disable buffering).

Unlike Rainbows::Base, this does NOT support persistent connections or pipelining. All Rainbows! specific configuration options are ignored (except Rainbows::Configurator#use).

RubyGem Requirements


Pages Classes Methods
mail archives: https://yhbt.net/rainbows-public/
	http://ou63pmih66umazou.onion/rainbows-public/ 
	nntp://news.public-inbox.org/inbox.comp.lang.ruby.rainbows 
	nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.rainbows 
	nntp://news.gmane.io/gmane.comp.lang.ruby.rainbows.general 
public: rainbows-public@yhbt.net
source code: git clone https://yhbt.net/rainbows.git
	torsocks git clone http://ou63pmih66umazou.onion/rainbows.git