RE: [coldsync-hackers] Re: Redux: Netsync + [X]inetd

["Brian Johnson" <bjohnson at jecinc dot on.ca>]

>There are two ways to do it:
>1) Start on incoming TCP/IP from inetd.conf - xinetd.conf  - requires
>modifications to treat stdin/stdout as TCP/IP connection
>2) Run as standalone server and use standard socket sequence - listen() -
>fork() - accept() - less modifications to ColdSync

>I would do 2)


You're way beyond me, I think I'll stick to trying to make conduits for
now - I think the smaller number of conduits is what makes Coldsync lag
behind pilot-xfer solutions right now (despite what I think are some major
benefits that Coldsync has).

With more conduits (and more feature packed ones than right now) and a
multi-user netsync system, Coldsync really becomes attractive to small and
medium enterprise system admins (IMO)


-- 
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.