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
