Re: [coldsync-hackers] Error when using coldsync from inetd.conf

[Rich Bowen <rbowen@rcbowen.com>]

> Alex Tronin wrote:
> 
> I did a bit of experiments with netsync-ing and I think how it should
> be done:
> Coldsync listening to UDP packets should be a separate server.
> What it does just listens to incoming packets and sends ACKs, nothing
> else ( it can check if TCP listener is running, in this case it can
> send NACK).
> Don't have to be multithreaded - UDP packets are easy to handle.
> 
> Another server would be TCP listener,
> There are three possible options how to make it:
> 1) to start from inetd.conf
> 2) have standalone parent server which spawns a child every time there
> is incoming connection ( like Apache )
> 3) have true multithreaded POSIX-style server
> What is the best ? Any opinions ?

I would think that it would rather depend on how many clients that you
are serving. If you have people syncing every few minutes, I would think
that launching it from inetd would be sufficient. If you have multiple
connections per minute, perhaps it would warrant a forking server. That
would seem way overkill in every situation that I'm involved in. I would
think that it would be rather uncommon to have a situation where you
have more than one connection at a time. What I would love to see is
something that I can put on a central server and have everyone sync to
it, and it certainly seems that setting this up as an inetd service
would be more than adequate.

-- 
Rich Bowen <rbowen@rcbowen.com>
Come see me at Apachecon! -- http://www.apachecon.com/

-- 
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.