Probably every major app that requires backend support will have created their own backend and protocol for interacting with it. It's not a problem, it's just work. I solve it just like I would any Java app that has Apache HTTPClient available. In fact, my Java code for dealing with backend stuff is pure java that I can use in any Java context, given HTTPClient and other pure java libs as infrastructure. The only extra stuff I have to do in the Android side is use loaders and some special configuration.
Doug On Jan 28, 4:31 pm, Kristopher Micinski <[email protected]> wrote: > All, > > This is to you developers who want to backend communication in your > apps. This need pops up naturally in many apps because there just > isn't any other way to do it. (For example, file exchange, syncs with > a server, etc..) Right now I think that there are a few up and coming > libraries and backend services, but my guess is that many of you roll > your own backends using rest and json. It feels to me like this > probably causes a lot of people problems, because there interface > between your app and your backend isn't really baked in to the > semantics of the programming language or Android platform, so you have > to develop the protocol and follow your nose while debugging to get it > right. Do people run into this problem, or is it in practice a > nonissue because you test it once and it's "obviously right?" (Same > question for security!) > > kris -- 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
