Re: Task dispatching
Re: Task dispatching
- Subject: Re: Task dispatching
- From: Scott Ribe <email@hidden>
- Date: Tue, 13 Sep 2011 10:55:12 -0600
On Sep 13, 2011, at 10:42 AM, Jon Sigman wrote:
> Design-wise, should I have a lightweight front-end process that accepts all inbound requests and then dispatch the requests to one of the other idling processes?
That is an extremely common idiom for servers. Whether you should do that, or multiple worker threads, really depends on your specific app.
- Multiple processes incur some more overhead in communicating data back and forth, but a crash in any single server process only affects a single client.
- Multiple threads allow the data to be handed off with no overhead, but a crash anywhere affects all clients.
And of course there are many many other considerations ;-) The first thing I'd look at, is what is going on for a couple of minutes while the program is coming up? Would that have to happen for every process???
--
Scott Ribe
email@hidden
http://www.elevated-dev.com/
(303) 722-0567 voice
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden