Announcing SPDY draft 2 implementation in nginx

Re:Announcing SPDY draft 2 implementation in nginx by chmod775 on Friday June 15, 2012 @08:59PM (#4119519)

Wait. Did I just read that right? They want to emulate a packet (or frame) based protocol on top of a stream protocol (TCP-Stream) which itself uses packets? That adds umm... how many overhead? Lets count:

- Data Link Layer (for instance Ethernet-Frames/Packets)

- IPv4/IPv6 - Packets

- TCP-Packets --> TCP-Stream

- SPDY-Frames --> Multiple Streams

- (Edit OK. Maybe not HTTP. Just insert here how they want to transmit the headers)

That way we not only send more useless data. We also have to dis- and reassemble everything twice.

Why not just extend the TCP-Protocol to support multiple streams? There's still unused space in the header and we have the possibility add additional options.

http://en.wikipedia.org/wiki/Transmission_Control_Protocol#T...

Am I missing something? I know that applications are not allowed to send raw TCP-Packets on most OSes by default. But most servers run Linux, which could be easily patched to support such additional features. (And webhosts will have some work to support that new protocol anyways)

I don't get it.

Edit: SCTP may be a suitable replacement for TCP as mentioned in some other comment. http://en.wikipedia.org/wiki/Stream_Control_Transmission_Pro...

[ Parent | on HN ]

Re:Announcing SPDY draft 2 implementation in nginx by X-Istence on Friday June 15, 2012 @09:43PM (#4119614)

SCTP requires OS support... putting SDPY on top of TCP/IP is just like any other protocol and doesn't require adding an entire new protocol that will have to be firewalled, will have to traverse across different devices that may or may not have SCTP available (such as older consumer routers).

[ Parent | on HN ]