March 14th, 2013, 12:35 AM
Creating XML-RPC server. Why?
This might sound really stupid but I've got to ask you this. I read this in a Devshed article:
My questions is WHY? There is already apache server on local host (or web server online) that runs php. What is the point of creating another one? The clients can make the request without XML-RPC. What is it that is not achievable without XML-RPC? What am I missing here? Thank you.
March 14th, 2013, 02:40 AM
You don't need a separate server. It's just saying that there is a server and a client. Exact same thing as for the Web.
March 14th, 2013, 05:22 AM
if you're looking for some means of communicating and invoking actions between two apps (eg client and server) then consider representational state transfer (ReST).
I found I was doing something similar before the coining of the name and the resulting fanfare around it, but the principles consolidate the thinking for you. ReST also gives to the freedom to be pragmatic in your approach to the implementation. You could choose to be a "restafarian" or you could take a common-sense approach
March 15th, 2013, 05:10 AM
March 15th, 2013, 05:12 PM
Thanks for the book. I downloaded it. I am gonna check it as soon as I finish this. It looks like most things I need to do can be easily done (with curl).
Originally Posted by Northie