From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Nagle algorithm
Date: Tue, 27 Nov 2001 15:39:32 +0100 [thread overview]
Message-ID: <03aa01c17751$54599d60$b6f7c6d4@cybercable.fr> (raw)
In-Reply-To: <200111270857.IAA07692@localhost.localdomain>
> I'm being a little simplistic here, but since there are assigned
> port numbers, why not have the bind/connect subsystems make the
> decision based on port, with a default for anything else?
Yes that is too simplistic. Potentially you have large N protocol
rules and some of those protocols do not behave in ways you can
predict or monitor without carrying around a huge amount of baggage.
A silly example is HTTP: It should be on port 80, but lots of
people like using 8080 or other strange port #s.
As other's have said, it should be left to the application.
So far, only TCP/IP has been discussed, but do you build all
those rules etc into all the other protocols as well?
I don't think so.
next prev parent reply other threads:[~2001-11-27 14:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 11:23 Sean M. Doran
2001-11-26 19:28 ` Dan Cross
2001-11-27 8:57 ` Steve Kilbane
2001-11-27 14:39 ` Boyd Roberts [this message]
2001-11-27 19:56 ` Steve Kilbane
2001-11-27 22:26 ` Boyd Roberts
2001-11-29 16:55 ` Matt
2001-11-27 10:16 ` Thomas Bushnell, BSG
2001-11-27 18:59 ` Dan Cross
-- strict thread matches above, loose matches on Subject: below --
2001-11-29 17:33 jmk
2001-11-27 11:28 forsyth
2001-11-27 11:00 forsyth
2001-11-27 5:31 David Gordon Hogan
2001-11-26 12:07 Fco.J.Ballesteros
2001-11-26 11:52 Fco.J.Ballesteros
2001-11-26 11:09 nigel
2001-11-24 10:48 forsyth
[not found] <rsc@plan9.bell-labs.com>
2001-11-24 5:32 ` Russ Cox
2001-11-24 20:04 ` Scott Schwartz
2001-11-24 3:26 Scott Schwartz
2001-11-23 11:58 forsyth
2001-11-26 11:07 ` Sean M. Doran
2001-11-26 19:22 ` Dan Cross
2001-11-27 10:16 ` Thomas Bushnell, BSG
2001-11-27 18:55 ` Dan Cross
2001-11-23 9:44 forsyth
2001-11-26 9:59 ` Thomas Bushnell, BSG
2001-11-22 13:24 forsyth
2001-11-22 13:29 ` Boyd Roberts
2001-11-23 9:34 ` Thomas Bushnell, BSG
2001-11-26 19:13 ` Dan Cross
2001-11-21 23:38 David Gordon Hogan
2001-11-21 23:59 ` Andrew Simmons
2001-11-22 9:57 ` Thomas Bushnell, BSG
2001-11-21 23:20 Andrew Simmons
2001-11-26 10:57 ` Sean M. Doran
2001-11-26 19:11 ` Dan Cross
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='03aa01c17751$54599d60$b6f7c6d4@cybercable.fr' \
--to=boyd@fr.inter.net \
--cc=9fans@cse.psu.edu \
/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).