On Thu, Jan 19, 2012 at 2:39 AM, Tom <[email protected]> wrote: > > I take it that this RPC method is the same method used by GWT, So, the > intention to use GWT, is a major differentiator in the decision to use this > wizard. Conversely, this RPC method is not very portable - if you might > need to develop an iPhone client then you would need to re-implement your > server interfaces using a more portable method.
If you wanted to have an app on GAE with a GWT web client and a native Android client, the wizard might fit your needs well. Google account are used for authentication and C2DM, so it fits fairly well with the platform. > > One last question... does this wizard (and these methods) tie me to GAE? It > doesn't appear to. I'd rather avoid getting locked in to GAE. > Not too hard to find out: check the generated server code. If it is using GAE native APIs, then, naturally, it is tied to GAE. Data access is using JDO, so you can in theory replace the native JDO provider with something else. The user part is tied to GAE and Google accounts. http://code.google.com/p/cloud-tasks-io/source/browse/trunk/CloudTasks-AppEngine/src/com/cloudtasks/server/DataStore.java The real question: what do you need? RPC? REST? Platform independence? Something else? -- 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
