I set up a small test upp (echo server/client). When i
run it inside the emulator, no problem, rpc server
answers and superwaba write response on listbox. But,
when i run the same code on the real superwaba VM (both
on ipaq and on windowsXP) it returns "Client problem:
header too long". I think this is caused by superwaba
poor socket implementation. Ive had similar problems
also with plain tcp sockets. Anyway, tnx for your
library, its very useful.
Logged In: YES
user_id=55018
The problem is linked to this Super Waba VM bug:
http://superwaba.sourceforge.net/cgi-bin/twiki/view/Main/Faq#When_I_try_to_read_a_value_from_
it can be solved by changing HttpSimpleClient.
I attach a simple diff to show how to solve the problem.
Bye.
SimpleHttpClient.java.diff (the first was inverted)
Logged In: YES
user_id=739444
I never received notice of this, I'm sorry it took so long
for me to follow up.
Anyway, I think this problem & fix may be obsolete with SW
4.5 and the most recent download of xmlrpc4sw (still v0.3).
The specification for readBytes changed and I updated the
xmlrpc4sw code to accomodate it. Another user had submitted
a similar bug to me personally. I fixed that and I think
this bug may be a duplicate of the previous one.
Yage, if possible could you download a fresh .zip of
xmlrpc4sw and test for this bug? That would be much appreciated.