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.<br>
<br><div class="gmail_quote">On Thu, Oct 21, 2010 at 3:55 PM, Thierry de Villeneuve <span dir="ltr"><<a href="mailto:thierryv@abac.com">thierryv@abac.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Dear Perl Mongers of San Diego,<br>
<br>
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.<br>
<br>
Well, this said, here is what brings me here today.<br>
<br>
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".<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
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 ;-)<br>
<br>
Thanks a lot,<br>
<br>
Thierry<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
San-Diego-pm mailing list<br>
<a href="mailto:San-Diego-pm@pm.org" target="_blank">San-Diego-pm@pm.org</a><br>
<a href="http://mail.pm.org/mailman/listinfo/san-diego-pm" target="_blank">http://mail.pm.org/mailman/listinfo/san-diego-pm</a><br>
</blockquote></div><br>