AppEngine RequestFactory or "Normal" approach?

Question

This is not a problem, rather as a general question X vs Y.

So, I am experimenting with c2dm on android using a server written in the google engine. Right now I'm using the "Android Connected Android Project" as a template with some code added. Thus, the generated code uses RequestFactory for a bunch of things, for example, registering / unregistering devices, sending messages, etc.

My previous experiences with backend communication existed to establish a connection to a servlet, write to it (json) and read the response (json).

So here's the question: What are the benefits (if any) of using RequestFactory to communicate with the application engine instead of just writing / reading from URLConnection input / output streams? Or is it really just a matter of taste?

Answer 1

One of the drawbacks of the factory query is that it is very slow when retrieving objects. The user servlet and the HTTP request are MUCH faster (10x-20 times faster!).

Send this message for more details RequestFactory slow on Android

Answer 2

I have not used it myself yet, but the main advantage, as I understand it, is that it is really easy to authenticate against the App Engine application with Android credentials. Doing this manually is a bit of a pain.