Hi, On Fri, 7 Sep 2012 07:25:38 -0700 [email protected] wrote:
> The simple way is to write a web service with Soap, or Thrift which I > am familiar with. Thus the client could use the perl http library like > LWP::UserAgent. > SOAP may be a lot of things, but it isn't anything but simple (despite the fact that the "S" stands for "Simple"): * http://www.shlomifish.org/humour/by-others/s-stands-for-simple/ * http://cafe.elharo.com/web/rest-vs-soap-a-parable/ Someone I know was given a SOAP web service that some .NET programmers gave for the API (because .NET makes it easy), and eventually could only hack to talk with it using curl and other low-level stuff (after trying many other higher level alternatives). Then, they found that the corresponding .NET client code could not talk to the service either (!). SOAP is a big can of worms and one should avoid opening it. If you are given a SOAP service and there is no alternative, then you may need to deal with it, but otherwise you should use REST-based services or JSON-RPC or the other suggestions from my post. Regards, Shlomi Fish > > > I am planning to design a simple client application to execute RPC > > (Remote Procedure Call) on a remote server. > > > > All I have managed to learn so far is to create a TCP socket using > > IO::Socket::INET. > > > > But I am not sure what to do next. > > > > Any pointers/help/online resources about the same would be helpful. > > > > Thanks, > > Parag > > > > > -- ----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ Perl Humour - http://perl-begin.org/humour/ Had I not been already insane, I would have long ago driven myself mad. — The Enemy and how I Helped to Fight It Please reply to list if it's a mailing list post - http://shlom.in/reply . -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] http://learn.perl.org/
