Thanks for the REST suggestion, are we able to accomplish the same set of functionality (i.e. custom objects being serialized) etc? Essentially can we accomplish the same set of things with REST (binary data, Objects being passed as arguments etc) as we do with XML-RPC (from Apache 3.1)
I will look into this, but just wanted some quick guidance before I dive down the wrong path. Thanks again for your input. On Nov 24, 1:25 pm, Mark Murphy <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > See the aild documents: C:\android\docs\reference\aidl.html > > AIDL is for cross-component communication (Activity to Service) inside > Android. AFAIK, it is not designed for use outside of Android, such as > in a client/server environment. > > > On Nov 24, 2:01 am, check_writer <[EMAIL PROTECTED]> wrote: > >> I tried implementing the ApacheXML-RPC3.1 as I normally would in a > >> Java 1.5 app in eclipse and got exceptions. > > What were the exceptions? > > >> Or ifXML-RPCis not possible, what are my options in the way of a > >> Client/Server app on Android. > > The simplest is a REST-style interface, using ordinary URLs and HTTP > verbs (GET, POST, PUT, DELETE). This is rather popular with > Internet-based services nowadays for their public APIs. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > _The Busy Coder's Guide to Android Development_ Version 1.4 Published! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
