#1: Yes, turn library compression off.
#2: About 7600 bytes is the maximum for a single post, but I would strongly
recommend breaking a transaction that large into a sequence of smaller
transactions. You have to partially URL encode the data or going through
Palm.net will cause you problems, so, depending upon what you send, your
max. packet may be smaller (since URL encoding expands the data). If you
use a 'chunk' type protocol with your server, your max upload is limited by
transmitter charge. You will also have much lower connection costs (unless
you are using the unlimited plan).
What I mean by chunk is: Post 1 - give me an upload ID, Reply - ID, Post 2
- ID, Chunk ID, first 2K (or whatever), Reply 2 - Chunk ID, checksum...
#3: About 60K with the current Proxy software. Again, either using the
Palm chunk system or your own will save you transaction costs. Your own
system could get you around the Palm.net limit.
#4: INetLib is not really TCP/IP based. Basically, there are request
blocks that go to the wireless paging system which, in turn communicates
with the Palm servers. You can muck around with mail transactions and
actually get mail sent, but it is probably a lot easier (and more robust,
given documentation and control of the system) to do things like mail via
your own Web server. IE, Palm VII -> Your Web server (port 80) ->
POP3/SMTP. Kind of like how Hotmail, etc. work.
Good Luck,
-jjf
-----Original Message-----
From: David Slotter [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 09, 2000 7:25 PM
To: Palm Developer Forum
Subject: INetLib Questions
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/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
