Re: Five Reasons Why Synchronous Networking Is Bad
Re: Five Reasons Why Synchronous Networking Is Bad
- Subject: Re: Five Reasons Why Synchronous Networking Is Bad
- From: Mark Pauley <email@hidden>
- Date: Thu, 5 Mar 2009 11:41:17 -0800
Right, my point was that you should be rolling your own socket manager
(and probably thread pool) at that point. You're getting to the point
at which threading becomes beneficial because you need concurrency to
handle all of the incoming packets.
On Mar 5, 2009, at 11:33 AM, Joel Reymont wrote:
On Mar 5, 2009, at 7:27 PM, Mark Pauley wrote:
You'll eventually hit the open fd limit, not to mention that you'll
choke the rest of the system as you'll be hogging the filesystem.
The open fd limit can be upped way beyond 1024.
On the one hand, this is server stuff and I haven't found Mac OSX to
be a great server. No point trying to use CFSocket for this.
On the other hand, you could easily have some kind of a client
monitoring a bunch of connections and you would have exactly the
same scenario.
---
http://tinyco.de
Mac, C++, OCaml
_Mark
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden