"Tom Zerucha" <[EMAIL PROTECTED]> wrote in message news:16635@palm-dev-forum...
> To quote the reference manual:
>
> ExgDBRead stops
> calling the read callback function after it receives the entire database
> (it knows when it's got it all based on the header information).
I'd call this imprecise, at best. It knows how many records/resources there
are based on the header information, but it knows when the last
record/resource is complete based on the readproc returning 0 in *sizeP.
> Read ExgDBRead docs again - if I return any error, it ends the
> transaction and deletes what it has received so far.
Correct. I thought that's what you wanted. I think I understand now. You
have a TCP/IP session that's not responding, but isn't completely dead, and
you haven't received any bytes yet in this call to the readproc. If you wait
to receive a byte, the Cancel button won't work. If you return zero bytes,
ExgDBRead will think the stream ended. If you return an error, ExgDBRead
will abort the operation. There's no way out!
I'll take this as a request for a new version of the ExgDB routines that
lets the readproc return "nothing received yet, but it's not necessarily
done" as well as "we're done".
--
Danny Epstein
OS Engineer, Palm Inc.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
