From: "Tony D." <lists@...>
Date: 2012-12-14T05:38:44+09:00
Subject: Re: XMLRPC and consuming non-standard sources

7stud -- wrote in post #1089019:

No, I think you are misunderstanding what I said above.  I know it is a 
non-conforming system to the XMLRPC protocol.  I did not build the 
system; I just have to utilize it.

My question was the XMLRPC::Client class builds a lot of the 
functionality you need without writing your own.  XMLRPC utilizes the 
NET::HTTP library; it builds the XML request and parses the response.

So my only question was, would it be a good idea to override MethodCall, 
creating the needed request XML format and then override the parser to 
consume the response OR should I just go ahead and roll my own.

I was looking for best practices; not only for my future self but also 
for other developers down the road to maintain this.

Yes, it sucks that the API manufacturer did not follow the standards, 
but I can't muck around with that I just need to find a solution.

If you have any input on the initial question, please post 'em.

Thanks again!

-- 
Posted via http://www.ruby-forum.com/.