all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mlang@delysid.org, emacs-devel@gnu.org
Subject: Re: datagram source port?
Date: Wed, 15 Jan 2020 10:49:33 +0100	[thread overview]
Message-ID: <m21rs1qcb6.fsf@gmail.com> (raw)
In-Reply-To: <m2v9qc9rcq.fsf@gmail.com> (Robert Pluim's message of "Thu, 19 Dec 2019 18:07:17 +0100")

>>>>> On Thu, 19 Dec 2019 18:07:17 +0100, Robert Pluim <rpluim@gmail.com> said:

>>>>> On Thu, 19 Dec 2019 17:43:46 +0200, Eli Zaretskii <eliz@gnu.org> said:
    >>> From: Robert Pluim <rpluim@gmail.com>
    >>> Date: Thu, 19 Dec 2019 11:41:41 +0100
    >>> Cc: emacs-devel@gnu.org
    >>> 
    >>> That seems fragile. Anyway, given that we have
    >>> set-process-datagram-address, I donʼt see why we couldn't add
    >>> set-process-datagram-source-address as well. Eli, something like this?
    >>> Or we could add an optional parameter to set-process-datagram-address
    >>> to mean 'set source'.

    Eli> The latter, IMO, because the code is very similar.

    Robert> OK. Iʼve fixed a very embarassing bug with IPv6, and need to test it
    Robert> with a datagram process in server mode. Iʼve added it to my long list
    Robert> for this weekend (but itʼs vacation time, which helps :-)

I took another quick look at this, and noticed that the windows port
doesn't support datagram sockets at all, although the underlying
Winsock does. Is there a reason for that?

Robert



  reply	other threads:[~2020-01-15  9:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19  9:12 datagram source port? Mario Lang
2019-12-19 10:41 ` Robert Pluim
2019-12-19 15:43   ` Eli Zaretskii
2019-12-19 17:07     ` Robert Pluim
2020-01-15  9:49       ` Robert Pluim [this message]
2020-01-15 16:27         ` Eli Zaretskii
2020-01-16  8:04           ` Robert Pluim

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=m21rs1qcb6.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mlang@delysid.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.