On Sat, Sep 09, 2000 at 01:05:38PM -0700, Greg Lutz wrote:
> It appears that the Exchange Library (on which the Exchange Manager
> is evidently layered) might have what we need, but it is
> unfortunately not documented. There are also four undocumented
> ("system-only") Exchange Manager functions that look promising:
> ExgConnect, ExgGet, ExgInit, and ExgNotifyReceive.
Create a beam-manager mini-app that sends and receives and sends just
tags identifying the versions of the reader and database(s). If the
tags indicate an update exchange should be made, it reverse beams a
request, and only then does the original palm beam the update - and/or
the second can beam an updated reader or database if it has newer
copies.
The exchange manager moves objects. Just define the update protocol
in terms of objects.
> For the moment, I am giving up on implementing the capabilities we
> want. But any advice, or information from Palm about future plans,
> would be much appreciated.
You can also do ircomm. I haven't added the new serial manager
support to zboxz (which does batch beaming), but I can send ymodem,
and if updated so it would use ircomm, ymodem sends the filenames and
dates so that could be used to accept/reject files in an update.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
