Hi everyone, i am currently developing a typical Client/Server Application with Android. My application is currently layered as follows:
On the Client side: - GUI Layer - Business Layer - Network Layer On the server side: - Network Layer - Ressource Layer (my app is a RESTful Webservice) - Business Layer - Persistence Layer That seems like a lot of layers, but i am actually quite pleased with the architecture and performance. my main struggle though is the business layer being a layer twice throughout the whole system, as i do some business stuff on the android client side and then send it as xml to the server where i am again doing some business stuff to actually persist data with hibernate. i just want to get some opinions on how you people accomplished a client-server architecture. the main "issue" is, that with android we can handle business stuff easily (unlike j2me) on the client side. what are your experiences and practices. i am not to familiar builidng client/server apps yet, so i appreciate your input! greetings! brian --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
