Talk:XML - Managing Data Exchange/RPC

Some things to be aware of:


 * Any user-input that's taken should be considered string when using it for making an XMLRPC request. This means you will have to check the string for valid/invalid XML characters.  Duh!  You knew that already.


 * If you are making a library for xmlrpc, it will be a pain to decide how to do the datetime.iso-whatever datatype. As a design decision, I decided that I would have a valid-int as string.  So before i do my string checking, i check to see if the string is numeric, and if so, is it specifically an integer above a certain number.  This may (read: probably will) really mess things up so i'm going to find some other way to explicitly type this parameter.  Something akin to a namespace identifier.


 * xmlrpc is easier than SOAP, but you can only make one request at a time.

-- mchrisneglia
 * Since no one using xmlrpc (web-apis, blog-apis such as metaweblog/livejournal api/blogger) is really supporting/using the  is it really necessary to implement? I would say only do it if you use it.  Otherwise, I would suggest sending the fields as strings or -in the case of an integer-based unix timestamp- send it as an int.