I wouldn't be too hasty about removing the JSON. XML will cost you more in terms of resources and connecting directly to a database is likely also going to be more costly (although without seeing the actual implementation, I can't be sure of that).
JSON is actually about as perfect as it gets for mobile devices... you could only get better by implementing your own protocol and even then your likely not going to save much. Also note that connecting directly to the database means that the database is exposed on the net in general and will present security problems. Although databases have security, they are not designed to ward off all the worms that are constantly probing a public address looking for a weak spot. You can deploy something like MongoDB (which presents it's data as JSON anyway) but it's not recommended. However, after rereading your post, I think you are attempting to put a web service between your app and the database. This is exactly how the rest of us will be doing it, but you don't need to get rid of JSON, in fact JSON is what 90% of the apps in the market will be using. If your asking how you build that web service, I recommend Jersey REST API as a good place to start. There are plenty of other frameworks out there for doing it though, so find one you like. - Brill Pappin -- 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
