I have a few INetLib Questions that I am trying to answer. If anyone knows
or can refer me to somewhere I can find these out, I would appreciate it.
First question:
I am programming the Palm VII in C using the INetLib API. I know that
Palm.Net is used to handling text data in the text/html and text/plain
formats as well as image/gif and image/jpeg. Since Palm.Net can handle image
files such as GIF and JPEG, I would like to know if I can send arbitrary
binary data through the gateway in either the compressed or uncompressed
modes of operation, and if there is anything I need to be aware of.
Second question:
What are the maximum number of bytes I can send via a POST operation? I have
found that I can exceed 256 bytes with it, and as a result it is more useful
to me than a GET operation. The problem is that I do not know what the
reasonable limits are to expect reliable operation.
Third question:
What are the maximum number of bytes I may receive when reading from a
socket? I have heard the number is around 7,500 bytes, but I would like to
know what the reasonable limits are to expect reliable operation.
Fourth question:
(I previously posted this one to the developer form with no response. I am
trying again just in case.)
Can anyone tell me from a communications protocol standpoint how iMessenger
works? From what I understand, iMessenger is an application program which
uses INetLib, just like Clipper, but unlike Clipper, the user runs this
application directly. From the documentation I have been able to glean, it
uses the "Palm messaging protocol". Digging into INetMgr.h, I see references
to some "mail traps" but nothing more.
All help is appreciated.
-Dave Slotter
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
