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: Thu, 16 Jan 2020 09:04:08 +0100	[thread overview]
Message-ID: <m2tv4vvnd3.fsf@gmail.com> (raw)
In-Reply-To: <83muao4rd1.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 15 Jan 2020 18:27:38 +0200")

>>>>> On Wed, 15 Jan 2020 18:27:38 +0200, Eli Zaretskii <eliz@gnu.org> said:

    >> From: Robert Pluim <rpluim@gmail.com>
    >> Cc: mlang@delysid.org,  emacs-devel@gnu.org
    >> Date: Wed, 15 Jan 2020 10:49:33 +0100
    >> 
    >> 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?

    Eli> This comment from nt/inc/ms-w32.h explains that:

    Eli>   /* And the select implementation does 1-byte read-ahead waiting
    Eli>      for received packets, so datagrams are broken too.  */
    Eli>   #define BROKEN_DATAGRAM_SOCKETS 1

Eek.

    Eli> (Let me know if you want me to explain what it means by "1-byte
    Eli> read-ahead".  Or just read the large commentary that starts around
    Eli> line 870 of w32proc.c.)

    Eli> I don't know enough about datagram sockets, but I hope you do, in
    Eli> which case the above comment ought to be the answer.

Yes, itʼs the answer. Some brave soul could no doubt rewrite the w32
select implementation to fix this, but thatʼs not me.

Robert



      reply	other threads:[~2020-01-16  8:04 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
2020-01-15 16:27         ` Eli Zaretskii
2020-01-16  8:04           ` Robert Pluim [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=m2tv4vvnd3.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.