MadMongers

I'm swimming in possibilities over here.  Anyone have opinions on PLRPC, XML::RPC,
SOAP:::Lite, or any of the other tools in the box for RPC type stuff?

So far SOAP::Lite is looking pretty darn cool.

-Ray Ferguson

SOAP is unequivocally awful. I'd say try JSON::RPC / JSON::RPC::Dispatcher.

I think "unequivocally awful" comes close especially if trying Apache Axis to .NET interop.  I still have nightmares from it.

One thing I dislike about working with XML is that the XML parsing
modules are mostly XS, and libxml2 C header files aren't installed on
many OSs by default.

Are the JSON parsing modules pure-Perl?

Jesse

On 07/17/2010 01:27 AM, steve@fisharerojo.org wrote:
> Steve_p wrote:
>
> I think "unequivocally awful" comes close especially if trying Apache
> Axis to .NET interop.  I still have nightmares from it.
>
> That said, I use JSON-RPC on a daily basis for work and love it.  The
> fact that it easily interops between most major languages as well as
> Javascript and Actionscript on the web frontend makes the best case for me.
>
> Steve
>
> On Tue, Jun 29, 2010 at 5:56 PM,  > wrote:
>
>     chrisdolan wrote:
>
>     It can be cumbersome, but "unequivocally awful" is way too strong.
>       In the past I've used SOAP::Lite to talk to Apache Axis, .NET, PHP
>     SOAP and Flash SOAP and I've been quite happy with its
>     interoperability.  The documentation of SOAP::Lite has traditionally
>     been rather poor, but it's very powerful.
>
>     Chris
>
>     On Jun 29, 2010, at 3:16 PM,      >      > wrote:
>
>>     preaction wrote:
>>
>>     SOAP is unequivocally awful. I'd say try JSON::RPC /
>>     JSON::RPC::Dispatcher.
>>
>>     View Online
>>    
>>
>>
>>
>>     Madison Area Perl Mongers - MadMongers
>>     http://www.madmongers.org
>
>     View Online
>    
>
>
>
>     Madison Area Perl Mongers - MadMongers
>     http://www.madmongers.org
>
>
> View Online
>
>
>
>
> Madison Area Perl Mongers - MadMongers
> http://www.madmongers.org

There are both XS and PP (pure perl) modules available.  "use JSON"
will intelligently grab the best one.  (Is JSON::Any deprecated?)  I
believe there is also JSON::Syck, though I'm not sure if XS or Syck
are better.  Anyone have any benchmarks?

On Mon, Jul 19, 2010 at 12:48 PM,   wrote:
> zjt wrote:
>
> One thing I dislike about working with XML is that the XML parsing
> modules are mostly XS, and libxml2 C header files aren't installed on
> many OSs by default.
>
> Are the JSON parsing modules pure-Perl?
>
> Jesse
>
> On 07/17/2010 01:27 AM, steve@fisharerojo.org wrote:
>> Steve_p wrote:
>>
>> I think "unequivocally awful" comes close especially if trying Apache
>> Axis to .NET interop.  I still have nightmares from it.
>>
>> That said, I use JSON-RPC on a daily basis for work and love it.  The
>> fact that it easily interops between most major languages as well as
>> Javascript and Actionscript on the web frontend makes the best case for
>> me.
>>
>> Steve
>>
>> On Tue, Jun 29, 2010 at 5:56 PM,  > wrote:
>>
>>     chrisdolan wrote:
>>
>>     It can be cumbersome, but "unequivocally awful" is way too strong.
>>       In the past I've used SOAP::Lite to talk to Apache Axis, .NET, PHP
>>     SOAP and Flash SOAP and I've been quite happy with its
>>     interoperability.  The documentation of SOAP::Lite has traditionally
>>     been rather poor, but it's very powerful.
>>
>>     Chris
>>
>>     On Jun 29, 2010, at 3:16 PM,      >      > wrote:
>>
>>>     preaction wrote:
>>>
>>>     SOAP is unequivocally awful. I'd say try JSON::RPC /
>>>     JSON::RPC::Dispatcher.
>>>
>>>     View Online
>>>
>>>
>>>
>>>
>>>     Madison Area Perl Mongers - MadMongers
>>>     http://www.madmongers.org
>>
>>     View Online
>>
>>
>>
>>
>>     Madison Area Perl Mongers - MadMongers
>>     http://www.madmongers.org
>>
>>
>> View Online
>>
>>
>>
>>
>> Madison Area Perl Mongers - MadMongers
>> http://www.madmongers.org
>
> View Online
>
> Madison Area Perl Mongers - MadMongers
> http://www.madmongers.org
>

JSON::XS outperforms Storable by a huge margin, Storable being the second-fastest serialization method in all of Perl.

I wrote JSON::RPC::Dispatcher, and would be happy to answer any questions you have about it.

I've used it in 1 minor and 1 major project so far. Both have worked like a charm.

I'd stay away from the SOAP stuff unless you control both the client and server. The problem is that SOAP has lots of different implementation types from language to language and provider to provider and SOAP::Lite doesn't cover all the variables. It's a good module, but not perfect.

If you must use XML, the XML::RPC module is a fair implementation.  

I second JSONRPC.  I've done a large project in XMLRPC, and I liked
the protocol but hated using XML.  The main reason is that you can't
count on XML to map to a Perl data structure like you can with JSON.
JSON->Perl and vice versa always works, which is really nice.  Also, I
don't find the extra features for XML like typing, stylesheets, etc.,
to be useful.  JSON is also much easier to webify (even easier than
XML) because you can just set the MIME type to be
application/javascript and there's no parsing/conversion necessary.

On Tue, Jun 29, 2010 at 3:46 PM,   wrote:
> jt wrote:
>
> I wrote JSON::RPC::Dispatcher, and would be happy to answer any questions
> you have about it.
>
> I've used it in 1 minor and 1 major project so far. Both have worked like a
> charm.
>
> I'd stay away from the SOAP stuff unless you control both the client and
> server. The problem is that SOAP has lots of different implementation types
> from language to language and provider to provider and SOAP::Lite doesn't
> cover all the variables. It's a good module, but not perfect.
>
> If you must use XML, the XML::RPC module is a fair implementation.
>
> View Online
>
> Madison Area Perl Mongers - MadMongers
> http://www.madmongers.org
>

As has been previously mentioned, SOAP::Lite and SOAP are difficult to deal with, and particularly, SOAP::Lite has had drastic API changes over the years, tragically breaking some of our stuff.

BUT, SOAP is a standard, and using SOAP::Lite and SOAP you can create services that interact with little problems between disparate systems.  We use a bunch of SOAP::Lite based Web Services to interact with SOAP Web Services written in Java, PHP and other languages and interacting with our ESB, among other vendor systems.

However, if you're just talking about your processes talking to your processes, it doesn't much matter what you do, as long as you do the same thing on either end (although, I wouldn't recommend reinventing the wheel, just use whichever of the available modules you want to use to magically communicate.)  :)

Note, though, that JSON doesn't always translate perfectly in-and-out of Perl either, there are a lot of exceptions in the JSON documentation (things like boolean values).  We rarely have problems with conversion from SOAP objects to Perl, but you do have to be conscious of what you are dealing with.

jon

On 6/29/10 4:41 PM, madtalk@madmongers.org wrote:

mcholste wrote:

I second JSONRPC.  I've done a large project in XMLRPC, and I liked
the protocol but hated using XML.  The main reason is that you can't
count on XML to map to a Perl data structure like you can with JSON.
JSON->Perl and vice versa always works, which is really nice.  Also, I
don't find the extra features for XML like typing, stylesheets, etc.,
to be useful.  JSON is also much easier to webify (even easier than
XML) because you can just set the MIME type to be
application/javascript and there's no parsing/conversion necessary.

On Tue, Jun 29, 2010 at 3:46 PM,   wrote:
> jt wrote:
>
> I wrote JSON::RPC::Dispatcher, and would be happy to answer any questions
> you have about it.
>
> I've used it in 1 minor and 1 major project so far. Both have worked like a
> charm.
>
> I'd stay away from the SOAP stuff unless you control both the client and
> server. The problem is that SOAP has lots of different implementation types
> from language to language and provider to provider and SOAP::Lite doesn't
> cover all the variables. It's a good module, but not perfect.
>
> If you must use XML, the XML::RPC module is a fair implementation.
>
> View Online
>
> Madison Area Perl Mongers - MadMongers
> http://www.madmongers.org
>

View Online

Madison Area Perl Mongers - MadMongers
http://www.madmongers.org

-- 
.Jonathan J. Miner----------------------------------------------------.
|  jon@jjminer.org  |      photos - http://photos.jjminer.org/        |
|                   | R.A.W. #1629 - http://www.reggaeambassadors.org |
|                   | LOCS Webmaster - http://www.locs-buffett.org    |
|  jabber/gchat: camrycurbhopper@gmail.com      AIM: camrycurbhopper  |
`---------------------------------------------------------------------'