Skip to main content

REST webservice with Android client vs RPC



We are still trying to decide between implementing a REST webservice vs going with RPC. Googles eclipse plugin makes it very easy to create an RPC service which is what the main attraction is for the RPC way. However, a REST service would seem to be easier to modify, IMHO, and would also allow for a future iOS client to connect with little or no rework. One concern I would have and maybe this is a problem with RPC also or indeed any Client-Server model is how do you modify your existing service and allow old clients to still work while allowing new clients to use the new functionality. What I mean is can you point me towards any thing we should look out for when modifying a web service so as not to break existing clients or force them to upgrade. Any links you have that would cover this would be appreciated




Comments

Popular posts from this blog

Slow Android emulator

I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?

CCNA 1 Final Exam 2011 latest (hot hot hot)

  Hi! I have been posted content of ccna1 final exam (latest and only question.) I will post the answer and insert image on sunday. If you care, please subscribe your email an become a first person have full test content. Subcribe now  Some question  have not content because this question have images content. So that can you wait for me? SUNDAY 1. A user sees the command prompt: Router(config-if)# . What task can be performed at this mode? Reload the device. Perform basic tests. Configure individual interfaces. Configure individual terminal lines. 2. Refer to the exhibit. Host A attempts to establish a TCP/IP session with host C. During this attempt, a frame was captured with the source MAC address 0050.7320.D632 and the destination MAC address 0030.8517.44C4. The packet inside the captured frame has an IP source address 192.168.7.5, and the destination IP address is 192.168.219.24. At which point in the network was this packet captured? leaving host A leaving ATL leaving...