[coldsync-hackers] Re: your mail

["Matthew C. Weigel" <weigel+@pitt.edu>]

[looks like the way cs.cmu.edu handles email is preventing me from
sending mail to the list - I've switched my subscription to here now]

On Wed, 24 Oct 2001, Andrew Arensburger wrote:

> DLP/PADP/SLP, whereas USB and network Hotsync use DLP over what I've
> called "netsync", for lack of a better term. The 'protocol' argument
> determines how pconn->dlp.read and pconn->dlp.write will be
> initialized.

?? PConnection_usb.c calls padp_init unconditionally, it appears to me. 
That is, listenType specifies (indirectly) whether dlp.read points to
netsync_read or padp_read.

> sample code showing how to use io_bind, io_connect, and io_accept is
> ColdSync itself, but if you're familiar with bind(), connect() and
> accept(), it'll make a bit more sense.

OK, so... looking at _usb.c, I can just ignore these three?

> 	pconn_osx_open()
> 	osx_read()
> 	osx_write()
> 	osx_close()

So if I'm following this, these are the four non-trivial functions to
implement, and

> 	osx_bind()
> 	osx_accept()
> 	osx_connect()
> 	osx_drain()
> 	osx_select()

are the trivial/noop functions?

> 	You'll also need to check which software protocol you're using
> (see the various "switch (pconn->protocol)" statements in
> PConnection_*.c).

I'm not seeing these - all I see are a few references to protocol in
slp_addr?

> 	Does this answer your questions?

And leave me with more, yeah :)
-- 
 Matthew Weigel
 Research Systems Programmer
 mcweigel@cs.cmu.edu ne weigel@pitt.edu

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.