Ksoap2 with https uses a lot of bandwitch How to optimize connections?

Question

I'm writing an app that connect to an https web service many times using ksoap2 and the data usage of the app is high. I think it's high because I'm doing the connection every time i invoke the WS.

There is a way to use the same connection for my application like a singleton or sharing the HttpTransportSE object?

An example of my code:

public boolean Call1_Example(String Param1, String Param2)
{

    SoapObject request = new SoapObject(NAMESPACE, METHOD_NAME24);
    SoapSerializationEnvelope envelope = new SoapSerializationEnvelope(
            SoapEnvelope.VER11);

    request.addProperty("Param1", Param1);
    request.addProperty("Param2", Param2);

    envelope.dotNet = true;
    envelope.setOutputSoapObject(request);
    HttpTransportSE androidHttpTransport = new HttpTransportSE(URL);

    Boolean resultado = false;
    Object response;

    try {


        androidHttpTransport.call(Method1_SOAP_ACTION,
                envelope);
        response = envelope.getResponse();
        resultado = Boolean.parseBoolean(response.toString());

    } catch (Exception e) {

        resultado = false;
    }

    return resultado;
}

areyou using asynctask or thread for network related operation? — Raghunandan, Jul 18 '13 at 06:49
Yes, the call is always in a asynctask. The code works ok but I think the app uses a lot of bandwitch. — David, Jul 18 '13 at 06:51
It was a mistake in my code that consumes the data, not the ksoap2 (I was doing a http post every time the app starts). Thanks for your support !! — David, Sep 24 '13 at 09:37

score 0 · Accepted Answer · edited May 23 '17 at 11:56

I faced the same problem. My WS always returned the whole object I requested. So I manage that the server stores for each object its last updated time by using System.currentTimeMillis() in every setters.

When you consume your WS you retrieve the response and keep the last updated time. For the next request to the WS, you'll send this stored time.

So the server will send you only the difference. Of course, it leads to a modification of your server's code.

I don't know if it's a clean solution, but it works fine. I've got approximatively the same time response in Wifi and in 3G.

You can also use gzip to compress the message.

HeaderProperty headerProperty=new HeaderProperty("Accept-Encoding", "gzip");

You can see a sample here

It's a good aproach thanks, but my problem was a mistake with an http request every time I started the app. — David, Sep 24 '13 at 09:39

Ksoap2 with https uses a lot of bandwitch How to optimize connections?

1 Answers1