<snip> > Unfortunately the number of > sockets is limited by a big number - 65535 and when your > stateless proxy should process 1000 incomming requests per > second you will reach the limit very fast - 65 seconds. In > this case when to close client connection is very important.
That is why it is acceptable to reclaim when needed. If you reclaim immediately, it causes useless re-opening of connections. > In case of transaction stateful entities you know about > transaction and you have to maintain connection opend during > transaction, It is desirable. However I'm unaware of it being a sip requirement since rfc3261 and rfc3263 discuss how to reopen the connection if needed. If there are security and/or nat issues preventing such behavior, that is what the outbound draft is trying to address. > in case of stateless one - when to close is not > defined. That is why I think the stateless proxy should close > TCP connection ASAP and to close connection immediately after > forwarding an incomming request is the only way to process > 1000 incomming TCP requests per second. It will likely hurt your performance instead of helping because you would potentially be reclaiming connections prior to actually needing to reclaim them. Thus you might be closing and reopening connections for no reason. > ----- Original Message ----- > From: "Brett Tate" <[EMAIL PROTECTED]> > To: "Victor Tsoukanov" <[EMAIL PROTECTED]>; > <[email protected]> > Sent: Wednesday, February 07, 2007 7:43 PM > Subject: RE: [Sip-implementors] Stateless Proxy and TCP transport > > > > > > So, in the case of a stateless proxy, > > > > the TCP connection would close > > > > once the SIP request had been successfully > > > > sent. So, the connection for the response > > > > would "Fail" and the response would be sent > > > > to the sent-by (generally). > > > > > > Ideally ! I prefer this solution :) - to close client > > > connection immediately after forwarding and explanation ! > > > > Yes, this might work and is allowed. However my > understanding of the > > best common practice these days is to keep sip related tcp > connections > > up until they need to be reclaimed. This helps reduce delays and > > processing overhead introduced by devices choosing to open > and close tcp > > connections for each transaction or dialog. > > > > > > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
