&#62; you'll implement this method and allow your users to invoke it via <a href="http://myservice.com/employee/simpson" rel="nofollow">http://myservice.com/employee/simpson</a><p>That's fine of course for the trivial example, but what if my third parameter is an array, and I want to see a sensible error if I pass a hash table? What are the rules for which parameters go in the URL, whether they are delimited by ".", "/", or something else, and when they come as JSON in the request body, and how many there are, and what format they should come in?<p>&#62;  find a library (or implement your own) that will generate all the needed XML files etc.<p>Is this a problem? Many many such libraries exist which make exposing RPC calls nearly as easy as writing function declarations. (After all, that's what it's for - remote functions.) When I'm writing normal functions, I don't pass a request type, and a parameter string with various arbitrary delimiters, along with a possible big blob of text, and use that to fit every possible function, dealing with it in my own individual ad hoc way, do I?