Note, I am not primarily interested in conduits at the moment.
You should be, because that will be your best solution.
Palm never intended to produce a handheld desktop computer
Indeed not.
and I don't wish to attempt to mis-apply the technology
You run the risk of doing exactly that. Palm always considered data transfer and
syncing to be an integral part of almost all PDA applications (in contrast to
the approach MS have taken with PocketPCs for example, where it is very much an
afterthought). Conduits are the recommended technique for supporting that. You
can do it other ways, but they are all more work, since they do not have
built-in support.
Now, there are problems and weaknesses with conduits (some of them addressed in
CDK 6), but you will not find a simpler way to do what you want.
Your product sounds interesting, but I recall reading something from Palm
Source that indicated that, as an example, a sales price list could be sent
out to salespeople for them to load onto their Palm devices once per month,
without a conduit.
You can, of course, but you have to write more code to be able to do it. Any
syncing logic you need has to be written whether or not you write a conduit. If
you do not use the built-in way (that is guaranteed to work on all PalmOS
devices) of getting data onto the device, then you have to also write the
transport layer (on both the PC and Palm ends). Now, there are valid reasons why
someone would want or need to do that. Doing it because it is simpler than
writing a conduit is most definitely not one of them!
Cheers,
Jim Cooper
__________________________________________
Jim Cooper [EMAIL PROTECTED]
Skype : jim.cooper
Tabdee Ltd http://www.tabdee.ltd.uk
TurboSync - Connecting Delphi to your Palm
__________________________________________
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
