Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | make sure the body finishes rendering before checking response closure | Aaron Patterson | 2012-08-03 | 1 | -1/+2 |
| | |||||
* | close the response when the response body is set so that normal render calls ↵ | Aaron Patterson | 2012-07-29 | 1 | -0/+9 |
| | | | | will work | ||||
* | header hash is duped before being sent up the rack stack | Aaron Patterson | 2012-07-29 | 1 | -0/+13 |
| | |||||
* | make sure set_response! sets the correct response object | Aaron Patterson | 2012-07-29 | 1 | -0/+6 |
| | |||||
* | Controller actions are processed in a separate thread for live | Aaron Patterson | 2012-07-29 | 1 | -3/+69 |
| | | | | | | | | | | responses. Processing controller actions in a separate thread allows us to work around the rack api - we can allow the user to set status and headers, then block until the first bytes are written. As soon as the first bytes are written, the main thread can return the status, headers, and (essentially) a queue for the body. | ||||
* | added live responses which can be written and read in separate threads | Aaron Patterson | 2012-07-29 | 1 | -0/+26 |