| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | header hash is duped before being sent up the rack stack | Aaron Patterson | 2012-07-29 | 1 | -0/+4 | |
| | | ||||||
| * | freeze the header object | Aaron Patterson | 2012-07-29 | 1 | -0/+5 | |
| | | ||||||
| * | make sure set_response! sets the correct response object | Aaron Patterson | 2012-07-29 | 1 | -0/+9 | |
| | | ||||||
| * | adding a more docs on closing response streams | Aaron Patterson | 2012-07-29 | 1 | -1/+4 | |
| | | ||||||
| * | pushing Buffer up to Live | Aaron Patterson | 2012-07-29 | 1 | -22/+22 | |
| | | ||||||
| * | adding some docs | Aaron Patterson | 2012-07-29 | 1 | -1/+26 | |
| | | ||||||
| * | Controller actions are processed in a separate thread for live | Aaron Patterson | 2012-07-29 | 1 | -2/+26 | |
| | | | | | | | | | | | 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. | |||||
| * | raise exceptions on header set after response committed | Aaron Patterson | 2012-07-29 | 1 | -0/+21 | |
| | | ||||||
| * | added live responses which can be written and read in separate threads | Aaron Patterson | 2012-07-29 | 1 | -0/+42 | |
 |
index : rails.git | |
| Mirror of official rails repo with custom fixes. | Harald Eilertsen |
| aboutsummaryrefslogtreecommitdiffstats |