I guess, the default Android's way is the best. Of course, you can add more libraries, but then that would be redundant. I hope Google has already taken care of the performance part.
Thanks and Regards, Kumar Bibek On Jan 2, 3:15 am, Frank Weiss <[email protected]> wrote: > Considering that the execute method's latency includes network and server > times, on what basis do you think it's taking too long? What latency are you > observing, less than one second, more than one minute? > > On Fri, Jan 1, 2010 at 1:19 PM, SizzlingSkizzorsProgrammer <[email protected] > > > wrote: > > Yes, I've tried logging and the HTTP execute definitely takes the > > largest chunk of time, but how can I speed it up? Is there another > > protocol/method? > > > On Dec 31 2009, 6:07 pm, jotobjects <[email protected]> wrote: > > > On Dec 31, 12:52 pm, SizzlingSkizzorsProgrammer <[email protected]> > > > wrote: > > > > > It works fine, but it's quite slow...any way to make it faster? > > > > A guess would be that the HTTP network speed is 100's of times slower > > > than all the rest of the code. You might log the time before and after > > > the execute method if you haven't already done that. > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected]<android-developers%[email protected]> > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
