mbelshe / spdy-specification Goto Github PK

I just want to inform of an issue I ran into while working with SPDY for the backend.
It's not really possible to queue SPDY requests using ZeroMQ (or similar), because the zlib session used for header compression makes streams depend on the state of the entire connection. That is, if requests (as SYN_STREAMs) are dispatched to multiple backend servers, header compression fails because each of the backend processes has it's own zlib session (and the session is stateful). This means that frontends cannot really multiplex the answers of the backend to a single socket, as each connection would require it's own zlib session.

Now, one way to resolve this would be to declare that SPDY is strictly meant for point-to-point communication.
Or, header compression could be made optional to make SPDY compatible with this use case.

Hi,
it looks that frame size is limited to 16,777,215 bytes (24bits), but the lengths of various fields within frame (number of name/value pairs, name length, value length) can be up to 4,294,967,295 bytes (32bits) in size, which doesn't really make sense (even if you account for compression).

More precisely, I see the maximum frame size as unnecessary restriction put in place for no good reason, especially when you consider frontend<>backend communications with buffering frontend. How about changing the frame size to 32bits or even 40bits?