Re: CFSocket freezes
Re: CFSocket freezes
- Subject: Re: CFSocket freezes
- From: Cameron Hayne <email@hidden>
- Date: Sun, 27 Nov 2005 15:13:59 -0500
On 27-Nov-05, at 12:53 PM, Chilton Webb wrote:
On Nov 27, 2005, at 11:29 AM, Cameron Hayne wrote:
But it is almost always preferable to implement the server as a
separate headless process as has been described earlier. The
various GUIs interact with the server as clients that just happen
to run on the same machine or the same local network as the
server. Or the GUIs just interpret the various log files produced
by the server without any interaction with the server.
How is it preferable?
- smaller, independent software components, each with well-defined
interfaces to the other entities (files, network clients, local
clients, etc) with which it communicates
- software development is non-linear: a component that does A & B
takes more development & maintenance effort than the sum of the
effort needed by independent components that do A & B separately.
- separate components can be developed by separate teams
- security considerations are vital for the server component; this is
far easier if it is as small and simple as possible, and if it uses
standard pre-tested software components as much as possible.
- modularity of design allows ease of introduction of other features
at a later time
- easier to test non-GUI components
- etc, etc
--
Cameron Hayne
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden