unicorn.git - Rack HTTP server for Unix and fast clients

Date	Commit message (Collapse)
2011-02-03	test/unit: fix tests under Ruby 1.9.3dev
	Ugh, one day I'll clean them up, one day...
2010-11-20	tests: stream_input tests for mixed gets/read calls
	Some apps may do them, so make sure we do them correctly.
2010-11-13	tee_input: restore read position after #size
	It's possible for an application to call size after it has read a few bytes/lines, so do not screw up a user's read offset when consuming input.
2010-11-11	add stream_input class and build tee_input on it
	We will eventually expose a Unicorn::StreamInput object as "rack.input" for Rack 2.x applications. StreamInput allows applications to avoid buffering input to disk, removing the (potentially expensive) rewindability requirement of Rack 1.x. TeeInput is also rewritten to build off StreamInput for simplicity. The only regression is that TeeInput#rewind forces us to consume an unconsumed stream before returning, a negligible price to pay for decreased complexity.
2010-10-07	start using more compact parser API
	This should be easier for Rainbows! to use
2010-10-05	tee_input: use kgio to avoid stack traces on EOF
	TeeInput methods may be invoked deep in the stack, so avoid giving them more work to do if a client disconnects due to a bad upload.
2010-10-05	test_tee_input: use a socketpair()
	It's a much closer representation of what we'd expect in the real server than a mono-directional UNIX pipe.
2010-10-04	tee_input: update interface to use HttpRequest
	This should ensure we have less typing to do.
2010-04-26	http: pedantic fix for trailer-less chunked requests
	HTTP requests without trailers still need a CRLF after the last chunk, that is: it must end as: "0\r\n\r\n", not "0\r\n". So we'll always pretend there are trailers to parse for the sake of TeeInput. This is mostly a pedantic fix, as the two bytes in the socket buffer are unlikely to trigger protocol errors.
2010-02-26	tee_input: avoid instance variables, it's a struct
	We'll use struct members exclusively from now on instead of throwing ivars into the mix. This allows us to _unofficially_ support direct access to more members easily. Unofficial extensions may include the ability to splice(2)/tee(2) for better performance. This also makes our object size smaller across all Ruby implementations as well, too (helps Rainbows! out).
2009-11-05	Util::tmpio returns a TmpIO that responds to #size
	Subclass off the core File class so we don't have to worry about #size being defined. This will mainly be useful to Rainbows! but allows us to simplify our TeeInput implementation a little, too.
2009-10-07	tests for read-in-full vs readpartial semantics
	We modified TeeInput to have read-in-full semantics in most situations to suit existing apps and libraries (like Rails) that don't check for and handle partial reads correctly. The read-in-full semantics are needed by Rails because of this: https://rails.lighthouseapp.com/projects/8994/tickets/3343
2009-09-08	"encoding: binary" comments for all sources (1.9)
	This ensures any string literals that pop up in our code will just be a bag of bytes. This shouldn't affect/fix/break existing apps in most cases, but most constants will always have the "correct" encoding (none!) to be consistent with HTTP/socket expectations. Since this comment affects things only on a per-source basis, it won't affect existing apps with the exception of strings we pass to the Rack application. This will eventually allow us to get rid of that Unicorn::Z constant, too.
2009-08-15	tee_input: make interface more usable outside of Unicorn
	TeeInput being needed is now (once again) an uncommon code path so there's no point in relying on global constants. While we're at it, allow StringIO to be used in the presence of small inputs; too.
2009-08-09	Switch to Ragel/C-based chunk/trailer parser
	This should be more robust, faster and easier to deal with than the ugly proof-of-concept regexp-based ones.
2009-07-16	move all #gets logic to tee_input out of chunked_reader
	This simplifies chunked_reader substantially with a slight increase in tee_input complexity. This is beneficial because chunked_reader is more complex to begin with and more likely to experience correctness issues.