[San-Diego-pm] SOAP server in PERL

Nicholas Wehr pm at bionikchickens.com
Thu Oct 21 16:21:59 PDT 2010

I've always opted for using XMLRPC instead as the WSDL support was shotty
for many years. I'm interested to hear what others have done here. At this
point - I'd be inclined to assert that Perl doesn't have great
interoperability with other soap implementations (like interacting w/ java
server/clients). this has been my experience in the past - I hope I'm wrong.

On Thu, Oct 21, 2010 at 3:55 PM, Thierry de Villeneuve <thierryv at abac.com>wrote:

> Dear Perl Mongers of San Diego,
> I very rarely post on the list since I've left San Diego in 2002. Few of
> you remember of me regularly attending the meetings ... that was some 10
> years ago !!!  I'm back to France now but have never unsubscribe from the
> list and long the days I was in SD.
> Well, this said, here is what brings me here today.
> I have this (big) project at the office where I'll need to build a SOAP
> server. The traffic is not expected to be very high: Something like a
> transaction every 10".
> All the business backend is already developed and I've started tinkering
> with SOAP::Lite a bit. I've never had to develop a server based on SOAP
> (HTTP-SOAP) before. So, it's a brand new situation for me. The XSD and WSDL
> is already developed, so far so good.
> If any one of you could shed some light on what are the "best practices",
> best options, best CPAN modules to consider looking at when to tackle this
> sort of project.
> The time to process one of the request will be important (around 10~20" ...
> creating a SQLite db file of a few thousand rows to hand over). I would
> rather consider an architecture where the server would fork a subprocess to
> take care of each request. This is this part I'm not feeling conformable
> with as of today.
> If someone could get me a few pointers where to start digging, that'll be
> awesome, specifically regarding the forking/threading issue.  Otherwise,
> I'll have to turn this part of the project to someone else to develop it in
> C++ and gSOAP. I'd like prove PERL can do the job here too ;-)
> Thanks a lot,
> Thierry
> _______________________________________________
> San-Diego-pm mailing list
> San-Diego-pm at pm.org
> http://mail.pm.org/mailman/listinfo/san-diego-pm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/san-diego-pm/attachments/20101021/4a79ab18/attachment.html>

More information about the San-Diego-pm mailing list