From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: dccp@vger.kernel.org
Subject: Re: [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SOCK_DGRAM
Date: Tue, 13 May 2008 16:23:25 +0000 [thread overview]
Message-ID: <20080513162325.GF15306@ghostprotocols.net> (raw)
In-Reply-To: <20080513072853.GB4514@gerrit.erg.abdn.ac.uk>
Em Tue, May 13, 2008 at 08:50:59AM -0700, David Stevens escreveu:
> Are they mutually exclusive?
>
> Why not add SOCK_DGRAM/IPPROTO_DCCP support while leaving
Because DCCP is not SOCK_DGRAM at all? :)
> the existing stuff alone, and then requiring programs that want to use
> getaddrinfo to use it that way?
I wonder what is the problem with doing what I did when adding support
for DCCP in ttcp, or for AF_LLC in ssh, ncftp, vsftpd, etc, i.e.
getaddrinfo/getnameinfo wrappers that look if SOCK_DCCP or AF_LLC are
being asked for and doing the right thing.
IIRC at the time I asked Ulrich Drepper about adding support for PF_LLC
sockets in glibc and he said that it would be OK as long as it didn't
included PF_LLC sockets in the default search, doing it only when PF_LLC
was explicitely passed. I just never got around to actually cook up the
patches and send it to Uli.
What would be the problem of SOCK_DCCP being handled in glibc in such a
fashion?
- Arnaldo
WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: Gerrit Renker <gerrit@erg.abdn.ac.uk>,
David Miller <davem@davemloft.net>,
dccp@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SOCK_DGRAM
Date: Tue, 13 May 2008 13:23:25 -0300 [thread overview]
Message-ID: <20080513162325.GF15306@ghostprotocols.net> (raw)
In-Reply-To: <OFDBD6E282.6F00998A-ON88257448.0056D40D-88257448.0057105E@us.ibm.com>
Em Tue, May 13, 2008 at 08:50:59AM -0700, David Stevens escreveu:
> Are they mutually exclusive?
>
> Why not add SOCK_DGRAM/IPPROTO_DCCP support while leaving
Because DCCP is not SOCK_DGRAM at all? :)
> the existing stuff alone, and then requiring programs that want to use
> getaddrinfo to use it that way?
I wonder what is the problem with doing what I did when adding support
for DCCP in ttcp, or for AF_LLC in ssh, ncftp, vsftpd, etc, i.e.
getaddrinfo/getnameinfo wrappers that look if SOCK_DCCP or AF_LLC are
being asked for and doing the right thing.
IIRC at the time I asked Ulrich Drepper about adding support for PF_LLC
sockets in glibc and he said that it would be OK as long as it didn't
included PF_LLC sockets in the default search, doing it only when PF_LLC
was explicitely passed. I just never got around to actually cook up the
patches and send it to Uli.
What would be the problem of SOCK_DCCP being handled in glibc in such a
fashion?
- Arnaldo
next prev parent reply other threads:[~2008-05-13 16:23 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 7:28 [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SOCK_DGRAM Gerrit Renker
2008-05-13 7:28 ` Gerrit Renker
2008-05-13 7:39 ` David Miller
2008-05-13 7:39 ` David Miller
2008-05-13 9:37 ` Gerrit Renker
2008-05-13 9:37 ` Gerrit Renker
2008-05-13 13:46 ` Gerrit Renker
2008-05-13 13:46 ` Gerrit Renker
2008-05-13 15:50 ` David Stevens
2008-05-13 15:50 ` David Stevens
2008-05-13 16:23 ` Arnaldo Carvalho de Melo [this message]
2008-05-13 16:23 ` Arnaldo Carvalho de Melo
2008-05-13 16:59 ` David Stevens
2008-05-13 16:59 ` David Stevens
2008-05-13 17:03 ` Gerrit Renker
2008-05-13 17:03 ` Gerrit Renker
2008-05-13 17:06 ` Rémi Denis-Courmont
2008-05-13 17:06 ` Rémi Denis-Courmont
2008-05-13 17:33 ` Arnaldo Carvalho de Melo
2008-05-13 17:33 ` Arnaldo Carvalho de Melo
2008-05-13 17:34 ` Arnaldo Carvalho de Melo
2008-05-13 17:34 ` Arnaldo Carvalho de Melo
2008-05-13 17:37 ` Rémi Denis-Courmont
2008-05-13 17:37 ` Rémi Denis-Courmont
2008-05-13 17:50 ` Arnaldo Carvalho de Melo
2008-05-13 17:50 ` Arnaldo Carvalho de Melo
2008-05-13 17:53 ` Arnaldo Carvalho de Melo
2008-05-13 17:53 ` Arnaldo Carvalho de Melo
2008-05-13 19:14 ` Ulrich Drepper
2008-05-13 19:14 ` Ulrich Drepper
2008-05-13 22:34 ` David Miller
2008-05-13 22:34 ` David Miller
2008-05-14 8:09 ` Gerrit Renker
2008-05-14 8:09 ` Gerrit Renker
2008-05-14 14:06 ` Ulrich Drepper
2008-05-14 14:06 ` Ulrich Drepper
2008-05-14 14:45 ` Gerrit Renker
2008-05-14 14:45 ` Gerrit Renker
2008-05-14 16:06 ` Ulrich Drepper
2008-05-14 16:06 ` Ulrich Drepper
2008-05-14 17:22 ` Gerrit Renker
2008-05-14 17:22 ` Gerrit Renker
2008-05-14 17:39 ` Sridhar Samudrala
2008-05-14 17:39 ` Sridhar Samudrala
2008-05-14 17:43 ` Ulrich Drepper
2008-05-14 17:43 ` Ulrich Drepper
2008-05-14 17:47 ` Rémi Denis-Courmont
2008-05-14 17:47 ` Rémi Denis-Courmont
2008-05-14 17:49 ` Rémi Denis-Courmont
2008-05-14 17:49 ` Rémi Denis-Courmont
2008-05-14 17:57 ` Ulrich Drepper
2008-05-14 17:57 ` Ulrich Drepper
2008-05-14 18:00 ` Gerrit Renker
2008-05-14 18:00 ` Gerrit Renker
2008-05-14 18:06 ` Ulrich Drepper
2008-05-14 18:06 ` Ulrich Drepper
2008-05-14 18:07 ` Ulrich Drepper
2008-05-14 18:07 ` Ulrich Drepper
-- strict thread matches above, loose matches on Subject: below --
2008-05-13 12:53 [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SO Remi Denis-Courmont
2008-05-13 12:53 ` [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SOCK_DGRAM Remi Denis-Courmont
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080513162325.GF15306@ghostprotocols.net \
--to=acme@redhat.com \
--cc=dccp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.