Actually there IS a relatively (6ish years old) precedent. Trumpet Winsock (a free-ware Windows TCP implementation that was VERY popular in the pre-win95 days before a certain evil monopoly decided to destroy the 3rd party TCP/IP stack market by (gasp!) actually including an implementation of TCP/IP in their product) had a hard-coded 2 connection limit. A windows machine running trumpet could ONLY connect to two remote sockets simultaneously without changing magic ini file parameters. Once again, we got burned horribly by that when we were testing the windows version of the Exchange client over trumpet - the instant you tried to talk to a second public folder server, the client failed in mysterious ways and I was the poor sod who got stuck with figuring it out.
So there ARE situations where connections are expensive. But not in a modern operating system. Larry Osterman -----Original Message----- From: Mark Crispin [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 11:22 PM To: Timo Sirainen Cc: [EMAIL PROTECTED] Subject: Re: speaking of storing flags On Mon, 28 Jan 2003, Timo Sirainen wrote: > Multiple > connections eat more memory and more network resources. How did you arrive at this conclusion? I suggest that you have fallen prey to an urban myth. Like most myths, there is a vestige of historical truth; in the NCP protocol used prior to 1983, network connections did consume costly resources. This was one of the things that TCP fixed. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate.
