"Jason Partyka" <[EMAIL PROTECTED]> wrote in message
news:43807@palm-dev-forum...
>#2 was what I meant... once you start receiveing data, getting a 0
means
>its over.
>As for stalls -- I've not had problems with that. Once data starts
>arriving, I read data, wait for another event, and let the
>inetSockReadyEvent tell me that I still have data to fetch. Eventally,
>I'll get that event, and when I read I'll get 0 bytes. When that
>happens, it is all done.
I understand that you haven't had stall problems, but is a stall
possible with the iNetLib? For example, it may not happen on palm.net,
but it may on OmniSky (whether or not this is true, I don't know). Is
information available on the differences between Palm.Net and OmniSky
and all the other iNetLib-compatible services?
------
Stalls are handled by this loop -- you read data only once. You then
re-enter the event loop, and if there is more data, you get a ready
event. If not, you wait in the event loop for the data to arrive. When
INetLib gets the last of the data, it sets the "ready" flag that causes
a ready event to be generated, but when you try to get that data, you
get 0 bytes. I've definitely seen stalls in getting data over the
Mobitex and CDPD networks -- but this loop handles them fine, since you
never read when there is no data to fetch, except at the end.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
