[Spread-users] Spread Configuration

[Mark Blackman]

On 31 May 2007, at 17:20, John Schultz wrote:

>
> A client's connection can either be to a "local" daemon on the same  
> machine using Inter Process Communicaiton, or it can be to a  
> "remote" daemon on another machine using TCP/IP.  If the client's  
> connection is local, then the client-daemon communication remains  
> within the machine -- no network bandwidth is consumed.  If the  
> client's connection is remote, then the client-daemon communication  
> goes over the network.

I wonder if you could elucidate on which cases you might ever wish to  
have a production system
client *not* talk to a local daemon. I.e. in general, should you  
always have one local daemon
per client machine in the best case?

Cheers,
Mark Blackman