androidHttpTransport.call() is very slow when i moved from android 2.2 to 2.3.3

[GoogleCodeExporter]

What steps will reproduce the problem?

1.try to call .Net Webservice with an 2.3.3 android

What is the expected output? What do you see instead?

i've checked response time of the server and it was very fast...
the problem is to get back the information sended back from the server.

i did:
Log (start Date)
 androidHttpTransport.call()
Log(End Date)

and in android 2.3.3 its like ten times waiting than 2.2.

What version of the product are you using? On what operating system?

android 2.3.3

Original issue reported on code.google.com by dnl...@gmail.com on 22 Nov 2012 at 9:00

[GoogleCodeExporter]

This might be related to some other setup of the device as well. What makes you 
think it is only related to ksaop and not e.g. the http stack. I have not had 
any performance differences between 2.2 and 2.3.x in my testing. You could have 
to dig deeper and find if the difference is actually by some code in ksoap or 
somewhere else in the call stack. If you find anything with more details please 
post here ..

Original comment by mosa...@gmail.com on 22 Nov 2012 at 5:01

[GoogleCodeExporter]

Hi, thanks for the quick response.
Ive tested and debug the application and i see that the call() method is
taking too long. For the tests Ive created new application that using one
of my web service methods with ksoap and with a simple http request and i
see that ksoap is 7 times slower than simple http req.

Original comment by dnl...@gmail.com on 22 Nov 2012 at 9:31

[GoogleCodeExporter]

yeah.. but it does all the parsing in that time. So really it is not that 
slow.. 

Original comment by mosa...@gmail.com on 22 Nov 2012 at 9:40

[GoogleCodeExporter]

Ive activated a login function that returning just one string "success". It
took 30 seconds. With http it took 2 seconds. Its realy so much for the
parsing? My biggest message is 300kb long

Original comment by dnl...@gmail.com on 22 Nov 2012 at 9:47

[GoogleCodeExporter]

Not sure... you would have to debug/trace into the call itself and see where it 
is loosing all the time..

Original comment by mosa...@gmail.com on 22 Nov 2012 at 9:57

[GoogleCodeExporter]

I will do this and let you know. Thank you.

Original comment by dnl...@gmail.com on 22 Nov 2012 at 10:02

[GoogleCodeExporter]

i continue to check and i see that its something with the dns server...
do you know what is my options?

thank you.

Original comment by dnl...@gmail.com on 25 Nov 2012 at 4:19

[GoogleCodeExporter]

You will have to figure this out yourself. At this stage it is NOT a ksoap 
issue and I will close the bug report.

Original comment by mosa...@gmail.com on 26 Nov 2012 at 7:36

• Changed state: Invalid