From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: Remi Denis-Courmont <rdenis@simphalempin.com>
Cc: netdev@vger.kernel.org, dccp@vger.kernel.org, Arnaldo <acme@redhat.com>
Subject: Re: [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SOCK_DGRAM
Date: Tue, 13 May 2008 14:46:31 +0100 [thread overview]
Message-ID: <20080513134631.GA7024@gerrit.erg.abdn.ac.uk> (raw)
In-Reply-To: <48a00ddc692de4b7b71273614e61ab17@chewa.net>
|
| DCCP clearly fails the POSIX definition of SOCK_DGRAM in different ways.
|
| I think this is not a good idea.
|
Thanks for the clarification. Even in Posix, datagram = connection-less.
Plus the issues with older kernel releases. Question resolved, no SOCK_DGRAM.
| > It also relieves the libc writers from having to support another socket
| > type.
|
| As long as SOCK_DCCP-or-whatever is not automatically selected when
| ai_socktype is nul, this should be both easy to implement in libc *and*
| backward compatible (applications will not try to use DCCP implicitly).
|
There are two possibilities:
* as additional supported protocol (there are many new transport
protocols, perhaps there is some kind of modular support),
* if DCCP service codes are part of the lookup, then getting library
support can take longer (algorithm changes).
Both may take a while until available. In the meantime it would be good
to find some smart workaround for getaddrinfo, as changes in the internals
so far required to fix applications several times.
prev parent reply other threads:[~2008-05-13 13:46 UTC|newest]
Thread overview: 30+ 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:39 ` David Miller
2008-05-13 9:37 ` Gerrit Renker
2008-05-13 15:50 ` David Stevens
2008-05-13 16:23 ` Arnaldo Carvalho de Melo
2008-05-13 16:59 ` David Stevens
2008-05-13 17:06 ` Rémi Denis-Courmont
2008-05-13 17:34 ` Arnaldo Carvalho de Melo
2008-05-13 17:53 ` Arnaldo Carvalho de Melo
2008-05-13 17:33 ` Arnaldo Carvalho de Melo
2008-05-13 17:03 ` Gerrit Renker
2008-05-13 17:37 ` Rémi Denis-Courmont
2008-05-13 17:50 ` Arnaldo Carvalho de Melo
2008-05-13 19:14 ` Ulrich Drepper
2008-05-14 8:09 ` Gerrit Renker
2008-05-14 14:06 ` Ulrich Drepper
2008-05-14 14:45 ` Gerrit Renker
2008-05-14 16:06 ` Ulrich Drepper
2008-05-14 17:22 ` Gerrit Renker
2008-05-14 17:43 ` Ulrich Drepper
2008-05-14 18:00 ` Gerrit Renker
2008-05-14 17:39 ` Sridhar Samudrala
2008-05-14 17:49 ` Rémi Denis-Courmont
2008-05-14 18:07 ` Ulrich Drepper
2008-05-14 17:57 ` Ulrich Drepper
2008-05-14 17:47 ` Rémi Denis-Courmont
2008-05-14 18:06 ` Ulrich Drepper
2008-05-13 22:34 ` David Miller
2008-05-13 12:53 ` Remi Denis-Courmont
2008-05-13 13:46 ` Gerrit Renker [this message]
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=20080513134631.GA7024@gerrit.erg.abdn.ac.uk \
--to=gerrit@erg.abdn.ac.uk \
--cc=acme@redhat.com \
--cc=dccp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdenis@simphalempin.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).