Hi there,
after some discussion here on the list, and talking to people on the
German Perl Workshop, I have the following plans for SOAP::Lite
1. drop support for perl 5.005 after the next stable release
Rationale:
5.005 requires several workarounds, mostly avoiding "use warnings", and
thus don't allow fine-grained warnings control.
Nobody seems to have a perl that old. While some systems (like HP-UX)
may still have 5.6.x as default perl, nobody I talked to has seen a
5.005 during the last years.
Impact:
Users with 5.005 won't be able to use newer SOAP::Lite versions.
2. Resolve namespace issues.
Rational:
The last SOAP::Lite picked by the CPAN module during a automatic release
is 0.60a. This is due to namespace issues: Modules like SOAP::Packager
conflict with other distributions.
I would like to move all SOAP::Lite specific stuff into the SOAP::Lite
namespace
Impact: Existing programs using __PACKAGE__ =~m/SOAP::/
&& __PACKAGE__ !~m/SOAP::Lite/ packages from the SOAP::Lite
distribution directly have to change their code.
Though this is a BIG change (which will break things), there's no way
around it: The only alternative would be to delete the SOAP package (and
possibly others) from CPAN - and there's people using it.
4. Move non HTTP Transport out of the main SOAP-Lite distribution and
flag the resulting distributions as unmaintained/looking for maintainer
Rationale:
Nobody seems to use non-HTTP transports.
Impact:
- The non-HTTP transport classes get no support from me any more. That's
hardly a change ;-)
- Other people interested in a specific transport can take over
maintenance for the transport layer they need.
4. Integrate WSDL based toolkits
Rationale:
I don't like the idea that a user has to pick from 4 different toolkits
(SOAP, SOAP::Lite, SOAP::WSDL, XML::Compile::SOAP) for just doing SOAP.
I'd like SOAP::Lite to be able to integrate different WSDL based
frameworks, so there's always the same API presented to the user.
Please tell me if one of these plans doesn't match your needs.
Martin
|
