Hello Mladen, > -----Original Message----- > From: Mladen Turk [mailto:mt...@apache.org] > Sent: Monday, March 12, 2012 8:24 AM > To: dev@tomcat.apache.org > Subject: Re: Possible alternative Tomcat IIS Connector implementation > > > I would rather see SPDY connector over AJP. > AJP has serious limitations, and recently we discussed using SPDY for > server-to-server communication. >
Thank you very much for your reply. I had a quick look at SPDY, and you're right, SPDY has features for using a TCP connection more efficiently (e.g. to multiplex streams over a single TCP connection). Maybe when I have some time again, I should look into creating an SPDY connector for IIS to Tomcat? :) However, currently I'm having a small doubt about a server-to-server communication with SPDY, but maybe it is only because I didn't look that much into SPDY, so please correct me if I'm saying something wrong now. >From what I read from SPDY specification, it allows to multiplex lot of >streams over a single TCP connection. E.g. when IIS would communicate to >Tomcat over SPDY, a single TCP connection would allow to process multiple >requests at a time. Now imagine that a Client with a very slow connection requests a file from Tomcat which is very big. IIS would create a SPDY stream over an existing TCP connection to start retrieving the file. However, When the stream is established and Tomcat begins to send the file, IIS would not be able to send all the chunks which it gets from the SPDY connection to the client immediately, since there is a very slow connection to the client. However, IIS can't simply stop reading from the SPDY connection, because there may be frames which belongs to other SPDY streams (e.g. other clients). This would mean that IIS needs to continue reading and cache the output from Tomcat somewhere, until the connected client reads it. Is this correct? (E.g. imagine a servlet creates dynamically 1 GB of data, which IIS would need to cache somewhere in order to be able to get chunks from other SPDY streams. Whereas with AJP, IIS would simply stop reading from the AJP connection which doesn't affect other clients.) Wouldn't this be a problem? (But probably I'm just missing something which allows to control this behavior). Thank you! Regards, Konstantin Preißer --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
