RE: MPA issue (3): Rejected Connection bit
"Teisberg, Robert" <[email protected]>
| Newsgroups | gmane.ietf.rddp |
|---|---|
| Message-ID | <717252EC3E37AE4392E2614EA24E9F2B07FDEB5D@txnexc01.americas.cpqcorp.net> |
> > The APIs make a distinction between a connection request > refused by the peer and those that failed for other reasons. There is room for disagreement whether APIs should conform to protocols or protocols to APIs. That's why I'm unconvinced by citing the authority of API specs. Especially in light of your other argument.... > This is an important distinction. If a connection failed for > "other" (non-peer) reasons, the chance of another session > request being honored is very low -- but the chance that the > same session will be accepted at some later time is good. > > If the connection was rejected by the peer, the opposite > is true. > > Generally the applications themselves do not care about > exactly what network error killed the connection, but there > is a very big difference between "cannot communicate > with X" and "X does not want to talk with you." > > I find this much more persuasive. That it keeps us out of the philosophical tarpit is a bonus. Bob