> For the future: > 0) I submitted a hasty patch to the uWSGI mailing list; a similar fix or > that one should be fine for "normal" http communication (i.e. expect > handlers to send 1 or 2 messages per http response -- then the > ring-buffer is OK) Alternatively 16 might just be way to small; bumping it up a bit is fine and still allows bounded resource usage on streaming; the idea was that streaming apps could adjust the message size for the total amount of outstanding data they wanted. > 1) Some mechanism to have Mongrel2 send files rather than streaming them > via a handler (I can easily hack my own app/handler) I'm working on that presently. Sending files in Mongrel2 sucks so I won't do any other features until this one is fixed > 2) Streaming apps like video may require extra thought for better > communication patterns between Mongrel2 and handlers Yep > > My 2 cents > > --Jeff >
