Hi Rémi,
El 13/05/2006, a las 12:14, Rémi Denis-Courmont escribió:
There are possibly more troublesome issues:
1/ how to handle UDP, which is also supported by getaddrinfo(), and has
more varied usages (not just socket() then connect())?
but this seems to be the natural behaviour...
i mean TCP is a connection oriented service, so it is possible for TCP
to determine if the connection is actually established and it is then
possible for TCP to determine if the selected address pair is working
and if not try with an alternative one.
In the case of UDP, it is a non connection oriented service, so it is
not possible for UDP to determine if the address pair is working, hence
it is up to the application that has selected the usage of UDP to
handel failures by themselves, i.e. to determine if the current address
pair is working and if not it is up to the app to try alternative ones.
so, as i see it, this result is completelly coherent with the type of
service provided by each of the transport layers...
regards, marcelo
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
