Date | Commit message (Collapse) | ||
---|---|---|---|
2009-03-21 | http11: don't set headers Rack doesn't like | ||
Fix the logic in HttpParser up front so we don't have to mess around with the following convoluted steps: 1. setting the HTTP_CONTENT_{LENGTH,TYPE} headers 2. reading the HTTP_CONTENT_{LENGTH,TYPE} headers again 3. setting the CONTENT_{LENGTH,TYPE} based on the HTTP_-prefixed one 4. deleting the HTTP_CONTENT_{LENGTH,TYPE} headers (since Rack doesn't like them) 1, 2, 3 were in the C code, 4 was in Ruby. Now the logic is: 1. if CONTENT_{LENGTH,TYPE} headers are seen, don't prefix with "HTTP_". All the branch logic for the new code is done at init time, too so there's no additional overhead in the HTTP parsing phase. There's also no additional overhead of hash lookups in the extra steps. | |||
2009-03-21 | unicorn/http11: remove GATEWAY_INTERFACE | ||
It's a CGI-ism and is not in the Rack spec, so don't bother. | |||
2009-03-10 | http11: mark private methods as static | ||
There's no point in increasing method visibility since it can cause conflicts with other libraries and reduces the inlining opportunities the compiler can make. | |||
2009-03-10 | http11: remove unnecessary CPP definitions | ||
2009-02-25 | rename http11 => unicorn/http11 | ||
Avoid conflicting with existing (and future) Mongrel installs in case either changes. Of course, this also allows us more freedom to experiment and break the API if needed... However, I'm only planning on making minor changes to remove the amount of C code we have to maintain and possibly some minor performance improvements. |