> -----Original Message----- > From: Vijay K. Gurbani [mailto:[EMAIL PROTECTED] > Sent: Friday, November 16, 2007 3:48 PM > > > With regards to TCP "persistent connection", where you mean the > > client can reuse the same TCP connection for requests going to the > > same server, is that really necessary to put in a standard? I mean > > it was always allowed, no? I guess it's good to make it explicit, > > but I'm not sure how one knows when it's the right thing to do or > > not. > > The subtle difference here -- unlike in HTTP -- is that there > are requests coming towards the client from the server. In HTTP, > the communication is one-way: the browser opens a connection to > the server and sends requests over that connection and can treat > that as a persistent connection for subsequent requests. AFAIK, > in HTTP the server does not send a *request* towards the client > (the browser) over that same connection.
Right, but that's why I say it's the same thing as TCP persistent connections in this draft. You're not allowing upstream requests over TCP, only over TLS. You're saying keep the TCP connection from the client to the server open, and send subsequent requests over it in the downstream direction (client->server). Requests going the other direction are sent over a TCP client->server connection from the other side. In that way it's exactly like HTTP/1.1. > > Like for example if the server side stuck something in > > the response to indicate "you may keep this connection open and send > > any future requests to me over it if you can". (i.e., the > > Connection/Keep-Alive header model as in HTTP) > > connect-reuse is arguing for this to be the default behavior in > SIP. Oh. Ok. > > Some vendors restrict how many simultaneous connections they'll allow > > from the same client, for security reasons, so are you thinking > > along those lines? > > Would that not in fact argue for persistent connections anyway? Sure, but it doesn't solve it. Persistent connections were always possible, so even if this new draft says to do it by default, the server has no way to know it is or isn't being done, and the client has no way to be told to do it. (not that I'm advocating that be done mind you) -hadriel _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
