Hi there,
I'm giving a talk about perl's current SOAP modules at the German Perl
Workshop in Erlangen from February 13 2008 to February 15 2008.
As far as I know from the preliminary schedule, the SOAP talk (the title
is "State of the SOAP" - stolen from Byrne's post last year) is
scheduled on Friday.
I'm also doing a Birds-of-a-Feather session on what people expect of
current SOAP toolkits.
Whether your going to Erlangen or not, I'd be interested in the
following points:
- What do you use SOAP::Lite for?
- for what purpose?
- on which platform?
- with wich perl version?
- in which (larger) Framework?
- as Client/Server?
- with which protocol?
- What do you use XMLRPC::Lite for?
... same as above
- What do you use UDDI::Lite for?
... same as above
There are two reasons for my interest:
The first is that I'd like to split up SOAP::Lite into several packages
to improve maintainability (I could imagine that the Jabber, Mail and
TCP transport backends become separate add-on-packages, or that
UDDI::Lite becomes a separate package), and I'd certanly like to keep
the stuff everybody needs in the core package.
The second reason is that "modern" Web Services with complex WSDLs and
stuff are a bit outside the scope of the current SOAP::Lite module - and
due to backward compatibility reasons it cannot be easily extended
(SOAP::WSDL and XML::Compile::SOAP, the current WSDL-supporting SOAP
toolkits both requires perl >=5.8, and SOAP::Lite even works with
5.005). I'd like to know how much backward compatibility SOAP::Lite
needs - and where. I could imagine that SOAP::Lite's core should run
with perls as old as 5.005, while new stuff like complete WSDL
processing (perhaps provided by a add-on) could require newer versions
of perl.
But... I don't know. But you do. Please help me out.
Regards,
Martin
|
