I would also not use serialized objects.. They are incredibly slow
compared to any other method.
For Googles' web services, I have connected directly from an Android
app, and have also used my server in between. I think it just depends on
whether the particular Google web service returns the data you want in a
format that is easy to use.
The reason I used my server was that I was needing as many results as
possible from Google Local Search, and they only return 8 at a time. The
extra processing and requests to do that on the phone made my app seem
slow, so I created a web service of my own to take the request from the
phone, ping Google Local search 4 times, consolidate the results, strip
out stuff the phone app didn't need, do error checking, add some extra
fields I wanted to pass back, change null data to a default, and then
return all of the results to the phone at one time. It made a HUGE
difference in the user perceived speed of the Android app because the
Android app only had to worry about displaying data that was already in
the format it needed.
The other benefit of processing on your server side is that if something
changes, many times, you can just update your server app without
changing the phone app at all.... The downside is that you are using a
little of your own bandwidth and server processing for every request.
As far as formats.... well... I didn't even consider SOAP because of the
extra overhead, and my app just doesn't need anything that SOAP
provides. For that JSON was the quickest both for bandwidth and for the
phone app to display the data.
Sincerely,
Brad Gies
-----------------------------------------------------------------------
Bistro Bot - Bistro Blurb
http://www.bgies.com
http://www.bistroblurb.com
http://www.bistrobot.com
-----------------------------------------------------------------------
Never doubt that a small group of thoughtful, committed people can
change the world. Indeed. It is the only thing that ever has - Margaret Mead
Dan Sherman wrote:
Outside of the question regarding Google's web services,
I would highly suggest against serialized objects. We've had a ton of
troubles using them in one of our test cases, speed, size, everything
about them :(
- Dan
On Fri, Feb 12, 2010 at 4:28 PM, Matt Kanninen <[email protected]
<mailto:[email protected]>> wrote:
Is anyone else trying to integrate an Android application with
Google's various WebServices? Do you tend to put a proxy server up in
between or do you just have the device hit Google directly?
What format is your data sent in? JSON? SOAP? Plain Old XML
objects? Java Objects serialized by Sun?
On one of my current projects we're still at an early planning stage.
Plus I want to know what to recommend.
Discuss!
-MK
--
You received this message because you are subscribed to the Google
Groups "Android Discuss" group.
To post to this group, send email to
[email protected]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:android-discuss%[email protected]>.
For more options, visit this group at
http://groups.google.com/group/android-discuss?hl=en.
--
You received this message because you are subscribed to the Google
Groups "Android Discuss" 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-discuss?hl=en.
--
You received this message because you are subscribed to the Google Groups "Android
Discuss" 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-discuss?hl=en.
