OS limits on incoming socket connections

Shed · 2002-01-15T14:06:09

Greetings all! I''ve recently become interested in the idea of writing some kind of multiplayer persistant world game, so I bought WordWare''s book on multiplayer game programming. One of the authors mentioned in passing that different operating systems have internal limits on how many sockets a server can be listening on at once. He went further to say that for some operating systems, this number may be as low as 5 or 6. Obviously, if I wanted to use streaming sockets, I''d run out of sockets fast on the server side. How do you guys get around this? Is this only a winsock thing? Why are these arbitrary software limits imposed on us? Does DPlay have similar limits? My current thinking to get around this problem is just to use UDP and send all the packets to the same server socket and let the server program sort it all out. I only have access to win98 and 2000 machines for use as potential game servers, so while Unix may in most cases be the answer, it isn''t here. Thanks for any input

Networking and Multiplayer Programming

Started by Shed January 02, 2002 11:20 AM

11 comments, last by Shed 22 years, 3 months ago

KalvinB

102

January 12, 2002 02:23 PM

Somebody mentioned the memory thing a long time ago but it was never verified. Thanks.

Ben

[ IcarusIndie.com | recycledrussianbrides.com | Got Linux? ]

Golthar

122

January 14, 2002 06:49 AM

Well, where I work we have several server products and according to experience, we can handle up to 3000 open sockets in Win NT.

As for memory.
We have a CVS server running on win NT (or win 2000) and when a person starts pulling downloads at a no delay rate (meaning he makes loads of connections) the VM memory goes up to about 500 mb.

Any good machine should be able to do more than 100 connections

"There is a $500 fine for detonating explosives within the confines of a city"

HJB417

122

January 15, 2002 02:06 PM

If there was a 10 connection limit, think about these online gameservers (Q3, HL), Heck, I''ve seen up to 64ppl on some tribes2 servers. The 10 connection limit they speak of applies to telnet, terminal services and I think their FIle/Printer sharing thing.

One problem with the programmer''''s mentality is insecurity. This goes deep. An insulting college litany says that failed mathematicians become computer programmers. They are also ridiculed for being nerdy losers, for being too fat or too skinny, and for having few social skills. Most programmers can be spotted easily in a crowd. Nobody really wants to hang out with them. Put thousands of these people in one company and if you can get them to work, you become a billionaire. -John C. Dvorak

--------------------------One problem with the programmer''s mentality is insecurity. This goes deep. An insulting college litany says that failed mathematicians become computer programmers. They are also ridiculed for being nerdy losers, for being too fat or too skinny, and for having few social skills. Most programmers can be spotted easily in a crowd. Nobody really wants to hang out with them. Put thousands of these people in one company and if you can get them to work, you become a billionaire. -John C. Dvorak

OS limits on incoming socket connections

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

OS limits on incoming socket connections

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines