HTTP_Spew::Request

Stores any exception that was raised in another thread (e.g. ContentMD5 or InputSpray write drivers).

Stores the Rack response (a 3-element Array) on success

May be called by some Rack servers such as Rainbows! to bypass to_path calls and avoid path lookups.

Creates a new Request based on a Rack env and input object and prepares it for writing to sock. input supercedes env since it may be an alternate IO object (such as one filtered through HTTP_Spew::ContentMD5.

sock may be the String representing an address created with Socket.pack_sockaddr_un or Socket.pack_sockaddr_in, or it may be an actual IO object with Kgio::SocketMethods mixed in (e.g. Kgio::Socket)

Called by Rack servers after writing a response to a client

Called by Rack servers to write the response to a client

Used internally by various HTTP_Spew elements to report errors across different Threads and Fibers

returns a 3-element Rack response array on completion returns :wait_readable or :wait_writable if busy Users do not need to call this directly, resume will return the result of this.

returns a 3-element Rack response array on completion returns :wait_readable or :wait_writable if busy

returns a 3-element Rack response array on successful completion returns an Exception if one was raised

Used by some Rack-compatible servers to optimize transfers by using IO.copy_stream