The problem w/ direct serial is that you have
to have your clients turn off their hotsync software
since it's hogging the serial port.
It would be nice if Palm provided a "serial pass-thru
API" to their hotsync manager, so programs running
on the PC could send data to the hotsync manager to
be written to the serial port ... but that ain't happening.
>From the other two choices, I would suggest writing
your own conduit, you have greater control over your
data in the long run.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
Mitch Fawcett wrote in message <10539@palm-dev-forum>...
>
>I have a project that requires an upload of data from PC to handheld. The
>quantity will vary between 200KB to 500KB. The data consists of exam
>preparation questions and answers. The transfer only needs to go one way;
>from PC to handheld. I will be encrypting the data to make it harder for
>someone to pirate the material.
>
>My question is, what is the best methodology for this sort of thing. I
have
>identified several options:
>
>1) Write a conduit.
>
>2) Use the serial API and file streaming to push the data up.
>
>3) Design a home-grown pdb maker to write the data into pdb format and use
>the backup conduit to suck the pdb into the handheld.
>
>If you know of other ways, let's hear 'em.
>
>I need to consider speed, reliability, user friendliness, and future
>support. I want to avoid having to rewrite the process as new PalmOS and
>Hotsync versions come out.
>
>Mitch Fawcett
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
