[EMAIL PROTECTED] schrieb:
Thanks for your kind response.
I can send plain text of two three lines to server succsessfully so after encode it and decoding at server side. I may guess that my http header is okay.
First, what encoding do you use? Does you WebServer support this >encoding?
I am doing simple encoding replacing white characters etc that is ESCencode and
URLencode. Yes my server supporting that.
So you are sending a binany file using ESCencode AND URLencode? How do
you tell this the WebServer? Usually you do this by adding a
header-string "content-encoding". How does your String look like?
My feeling is that using two Encodings is too much. You should use only
Base64 encoding. This is simple, fast and supported by every WebServer.
Second, is the file you create with ExgDbWrite still OK?....
I have tried with VFS by writing VFSFileWrite code in ExgDbWrite's Callback
function, its creating valid file.
OK. Thats good.
Third, how does the data look like on the server? Is it just >scrambled data or
is it close to what you expect?
I am getting data close to what I am excpecting.
Yeah, maybe this is the result of using 2 improper encodings. Switch to
Base64.
Thomas
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
