> [EMAIL PROTECTED] wrote:
> >
> > my proposal:
> > define NI_UDP as replacement of NI_DGRAM. deprecate NI_DGRAM (keep
> > it as an alias to NI_UDP is okay). define NI_SCTP, NI_DCCP and such.
> > these three are mutually exclusive, and if more than one is specified
> > it would cause EAI_FAIL.
>
> Hi Itojun,
> > my proposal:
> > define NI_UDP as replacement of NI_DGRAM. deprecate NI_DGRAM (keep
> > it as an alias to NI_UDP is okay). define NI_SCTP, NI_DCCP and such.
> > these three are mutually exclusive, and if more than one is specified
> > it would cause EAI_FAIL.
> Agree! I assume "and such" implies that NI_TCP will be defined too,
> which is still the default if nothing is specified in the call (for
> backward compatibility?)
yup, NI_TCP would have a value of 0 and is still a default.
itojun
-
> > now we have couple of new transport protocols coming, such as SCTP and
> > DCCP. how can we support service name lookup for those? i.e.
> > how can we tell getnameinfo(3) to use "sctp" or "dccp" for the 2nd
> > argument of getservbyport(3)?
> >
> > my proposal:
> >
> now we have couple of new transport protocols coming, such as SCTP and
> DCCP. how can we support service name lookup for those? i.e.
> how can we tell getnameinfo(3) to use "sctp" or "dccp" for the 2nd
> argument of getservbyport(3)?
>
> my proposal:
>
We should do this as addendum to 3493 for sure.
/jim
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of [EMAIL PROTECTED]
> Sent: Thursday, December 11, 2003 3:44 AM
> To: [EMAIL PROTECTED]
> Subject: getnameinfo and various protocol types
>
>
>
[EMAIL PROTECTED] wrote:
getnameinfo(3) specification assumes that there are only two transport
protocols - tcp and udp. when performing service name lookup
it would use "tcp" if NI_DGRAM is not specified, and "udp" when
NI_DGRAM is specified.
now we have co
Hi Itojun,
> my proposal:
> define NI_UDP as replacement of NI_DGRAM. deprecate NI_DGRAM (keep
> it as an alias to NI_UDP is okay). define NI_SCTP, NI_DCCP and such.
> these three are mutually exclusive, and if more than one is specified
> it would cause EAI_FAIL.
[EMAIL PROTECTED] wrote:
>
> my proposal:
> define NI_UDP as replacement of NI_DGRAM. deprecate NI_DGRAM (keep
> it as an alias to NI_UDP is okay). define NI_SCTP, NI_DCCP and such.
> these three are mutually exclusive, and if more than one is specified
> it would cause EAI_FAIL.
And define NI_
getnameinfo(3) specification assumes that there are only two transport
protocols - tcp and udp. when performing service name lookup
it would use "tcp" if NI_DGRAM is not specified, and "udp" when
NI_DGRAM is specified.
now we have couple of new transport pr
10 matches
Mail list logo