Switch to new writeUInt32BE / readUInt32BE Buffer methods.
Try to retain backwards compatibility, but 0.5.4 is a complete loss, so exclude it from the list of supported engines.
It is often desirable to push large data sets *after* the original response has been sent. This change should allow for that. I have tried to maintain backwards compatibility with the old push API. Also included is the last-modified header, which Chrome requires for certain resource (CSS).
Use optional object literal to drive use of the HEADERS dictionary in ZLib compression (retaining behavior that no args implies a dictionary).
Piped streams are destroyed when connections are terminated.
* Separate PushStream class (can probably be merged with Response) * New vows for push * Test server for push that runs on 8082 * The Response invokes the push callback with itself: - Allows access to request/response info - Allows access to stream ID - Gives callback access to push and pushFile methods - Examples in the test push server * Can push multiple files
Otherwise it bleeds into the primary flag byte position.
…API, send settings frame after SYN_REPLY
Parser need an empty end() method. Signed-off-by: François de Metz <firstname.lastname@example.org>