Re: Clustered Perl Applications?

[IlyaM]

Other alternatives:

• XML-RPC
• REST (see here, here and here).

Lot of interesting links on web services can be found on this page.

Currently I'm working on the project which involves distributed web services and after carefully examining SOAP and REST we have decided to go REST way. One of motivations is that SOAP is extremly blotated standard which adds a lots of complexity which in most cases doesn't solve problems which cannot be solved REST way. Do not be fooled by simplicity of SOAP::Lite API - read specs to get idea how complex is it.

--
Ilya Martynov, [e-mail]
CTO IPonWEB (UK) Ltd
Quality Perl Programming and Unix Support UK managed @ offshore prices - http://www.iponweb.net
Personal website - http://martynov.org

[sri]

I know what a monster SOAP is.
But I have to send big amounts of structured data in both directions.
And as far as I know, this is not a strength of REST.

[Matts]

Hmm, this is an ideal application for REST - your data can be converted to just XML. This is parsed much faster than SOAP (despite that also being XML) because it's 1 less layer to go through.

[sri]

Sure, REST sounds good, and perl structures can be easily converted to xml using XML::Dumper.

But why is it parsed so much faster? As you said it's also xml?

Especially i noticed the lack of documentation for REST!

But it might also be the frequent use of the word "rest" and the fact that Google is case insensitive. :)

Are there any examples/tutorials for REST/apache/mod_perl or even perl?