- From: Henrik Nordstrom <henrik@henriknordstrom.net>
- Date: Fri, 26 Jun 2009 02:18:52 +0200
- To: leighton@mail.eecis.udel.edu
- Cc: Mark Nottingham <mnot@mnot.net>, ietf-http-wg@w3.org, fred@cisco.com, amer@cis.udel.edu, prenatar@cisco.com
tor 2009-06-25 klockan 16:53 -0400 skrev leighton@mail.eecis.udel.edu: > Can you elaborate on your comment about trying to map multiple pipelined > TCP connections to a single SCTP association not working out well? > Thanks. Sorry, should have said multiple TCP connections vs a single SCTP association. It's not related to pipelining but the differences in transport level (in HTTP terms) signaling between multiple TCP connections and a single SCTP association. The main problem there is selective stream cancellation by the client. If all pending requests is to be canceled together then this is not an big issue, just tear down the SCTP association and be done with it. But if you need to more selectively cancel requests (i.e. a big download you accidently started) without breaking the other concurrent pending requests then things get a little trickier.. In the TCP case (non-pipelined) the client just closes that TCP connection which terminates that requests with no impact on the other requests. Regards Henrik
Received on Friday, 26 June 2009 00:21:51 UTC