>There was some interest last week on why I needed to know this but I havent
>heard back since then.
Right, sorry, I hadn't responded immediately since I didn't know the
answer, and then the note got lost in the pile of stuff that I'm doing all
at the same time :-(
>The reason why I need to know is because when I'm downloading data
>wirelessly I want to know if it's a regular Palm (or one with an OmniSky
>modem) in order to use straight TCP/IP or if it's a Palm VII so that I
>branch out in my code and then use the Inetlib functions.
So I think the real question this boils down to, is "should I use INetLib
or should I use NetLib, on a machine which has both installed?" Right?
That way we don't need to make product name assumptions, or limit ourselves
from running properly on a device by licensee XYZ which has free 100
megabit/sec wireless connectivity worldwide. (It is coming to the market
next week, but don't tell anyone.)
One answer is that if INetLib is there, you might as well use it because it
is the safer case: it works both on Palm VII devices as well as
OmniSky-enabled Palm V devices. And upon further thought, that seems like
a pretty good general answer... if it is there, why not use it?
One thing that'd be missing is a concept of which is more efficient... but
we don't have anything that would give that sort of indication. Or is
there another reason that you'd not want to use INetLib? Perhaps there are
some characteristics which the OS could give you hints about.
-David Fedor
Palm Developer Support
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
