[Home] [Groups] - Message: [Prev in Group] [Next in Group]

nu.kanga.list.mud-dev

19170: RE: [MUD-Dev] Re: TECH: Distributed Muds

[Full Header] [Plain Text]
From: "Jon Lambert" <tychomud@ix.netcom.com>
Newsgroups: nu.kanga.list.mud-dev
Date: Fri, 4 May 2001 00:56:16 -0400
References: [1]
Organization: Kanga.Nu
Matthew D. Fuller wrote:
> On Wed, May 02, 2001 at 08:12:03PM -0400 I heard the voice of
> Jon Lambert, and lo! it spake thus:
>> Caliban Tiresias Darklock wrote:
 
>>> generally assume you will never have more than 64 sockets in an
>>> FD_SET. ;)
  
>> What do BSD and Linux assume to be the FDSETSIZE to be?  Both
>> require you to #define FDSETSIZE should you want something else.
 
> /usr/include/sys/types.h:#define        FD_SETSIZE      1024
> (FreeBSD 5.0-CURRENT)
 
> On a 386BSD 0.1 system (don't *EVEN* ask), I see:
> #define FD_SETSIZE  256
> in <sys/types.h>

I think perhaps the implications or importance FD_SETSIZE as it
relates to NT might be misunderstood, because of it's importance in
unices.  Then again maybe not.

See here http://www.nightmare.com/medusa/descriptor_limits.html

FD_SETSIZE has no impact on the NT kernel.  It's only purpose is 
in defining the default size of fdset.  That is to say it can be 
changed at a programmer's whim without any other action. 

The limits on socket (fds) are based on the socket stack 
(winsock2.dll) and are vendor dependent and queryable.  

--
--* Jon A. Lambert - TychoMUD        Email:jlsysinc@ix.netcom.com *--
--* Mud Server Developer's Page <http://tychomud.home.netcom.com> *--
--* If I had known it was harmless, I would have killed it myself.*--
 
_______________________________________________
MUD-Dev mailing list
MUD-Dev@kanga.nu
https://www.kanga.nu/lists/listinfo/mud-dev