Hacker News new | past | comments | ask | show | jobs | submit login

I think you might be a bit confused here. The point of a server (http, gopher, or otherwise) is to serve as many clients fully as possible as quickly as possible. What you are talking about appears to be making lots of outbound connections from a client side application, which I think most people know is bad.

Or are you suggesting you've been burned by putting servers behind consumer grade routing and switching equipment?




Like I said initially, my concern is only tangentially related to the server stack.

Oh I'm not advocating serving less clients at the server or even limiting the sockets available at the server. It's purely a critique of the number of sockets per client. Not the overall number of sockets the server supports.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: