From: "Dave Korn" <dave.korn@artimi.com>
To: "'the sound of one packet flapping'" <cygwin-talk@cygwin.com>
Subject: RE: sending an empty UDP packet.
Date: Fri, 30 Jun 2006 13:27:00 -0000 [thread overview]
Message-ID: <000a01c69c48$f81482f0$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <20060630110904.GS18873@calimero.vinschen.de>
On 30 June 2006 12:09, Corinna Vinschen wrote:
> On Jun 30 19:18, Tanaka Akira wrote:
>> Hi. I have a trouble to send an empty UDP packet.
>
> Thanks for the bug report and especially the testcase. It's incredible
> but the check for a zero length packet has been introduced in 2002, 4
> years ago, and nobody has ever complained that it's wrong. Wow. Almost
> embarrassing.
>
> I've fixed that in current CVS. Check the next snapshot from
> http://cygwin.com/snapshots or wait for 1.5.20, which is really
> due soon now.
Sending no data with unreliable delivery (of that no data) is a bit too zen
for most, I guess ...
cheers,
DaveK
--
Can't think of a witty .sigline today....
next parent reply other threads:[~2006-06-30 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060630110904.GS18873@calimero.vinschen.de>
2006-06-30 13:27 ` Dave Korn [this message]
2006-06-30 13:34 ` Corinna Vinschen
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='000a01c69c48$f81482f0$a501a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=cygwin-talk@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).