CODEWITHSUNDEEP
androidgoogle-app-engineandroid-c2dmrequestfactory
Tomas
Tomas

Reputation: 1419

AppEngine RequestFactory or "Normal" approach?

This is not really a problem, more like a general X vs. Y question.

So I'm experimenting with c2dm on android using a server written in google app engine. At the moment I'm using the "App Engine Connected Android Project" as a template with some added code myself. So the generated code use RequestFactory for a bunch of stuff, like registering/unregistering devices, sending messages, etc.

My previous experiences with backend communication has existed of setting up a connection to a servlet, writing to it (json) and reading the response (json).

So here's the question: What are the benefits (if any) with using the RequestFactory for communication with the app engine instead of just writing/reading from an URLConnection's input/outputstreams? Or is it really just a matter of taste?

Upvotes: 4

Views: 482

Answers (2)

Vincent Vettukal
Vincent Vettukal

Reputation: 1051

One disadvantage of request factory is that it is very slow in retrieving objects.. A custom servlet and http request are MUCH faster(10x-20x faster!).

Check out this post for more details RequestFactory slow on Android

Upvotes: 1

Nick Johnson
Nick Johnson

Reputation: 101149

I haven't used it myself yet, but the main benefit, as I understand it, is that it makes it really easy to authenticate against the App Engine app with your Android credentials. Doing that by hand is a bit of a pain.

Upvotes: 0

Related Questions