I just tried sending 7K and it worked fine.  FWIW, 8.5K is really
pushing it for post data.  Both in terms of the Inet Library and the VII
transmitter.

Having mapped out memory usage to some extent, I would generally put
about 7600 bytes as the upper limit for reliable transmission for INet
with a modest PRC.  The other issue is the transmitter.  If you watch it
on an RF meter you can see that power drops off pretty quickly.  Errors
and retries are the norm, so if you are not getting a rock solid
wireless connection a big transfer is not going to go through.

One thing I didn't try today was a response which is not formatted as an
HTML page.  I'll try raw binary transfers later today (I'll have to
scrounge up some AAAs for the VII - the thing should have a spring
loaded magazine, like a semi automatic hand gun).

-jjf

-----Original Message-----
From: Robert McKenzie [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 03, 2000 9:02 AM
To: Palm Developer Forum
Subject: Palm.net snafu


In the last few days I have started to suspect that palm.net,
the wireless palm proxy server, has gone south.

I particular, I have an application that uses low-level INet
library calls (an HTTP POST) to communicate with our server.
Last Friday my app started to get an inetErrRequestTooLong
error in response to an INetLibSockHTTPReqSend with an 8.5KB
message (previously we had been able to send messages of that 
size).  Both Friday and today, a perfectly normal (not nearly
so large) POST makes it to our server just fine, but its equally
perfectly normal response does not make it back (I get a normal
inetSockReadyEvent, but the INetLibSockRead call returns an
actBytesP (actual bytes read pointer) value of 0 (zippo, nada,
zilch).

Did one of our good friends at Palm "update" the Palm.net server?

-bob mckenzie
<[EMAIL PROTECTED]>

-- 
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palm.com/devzone/mailinglists.html

-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palm.com/devzone/mailinglists.html

Reply via email to