Good luck! SOAP::Lite is a scary place =p
There was some talk of a reworking of SOAP::Lite in the past, but I'm
not sure what came of it.
+--------------------------------------------------------+
| Matthew Runo
| Zappos Development
| mruno@...
| 702-943-7833
+--------------------------------------------------------+
On Sep 27, 2007, at 5:15 AM, Martin Kutter wrote:
> Hi Byrne,
>
> as far as I can see, SOAP::Lite is currently not being maintained.
>
> In my opinion, this is a quite undesirable state, as SOAP and
> XMLRPC applications
> become more and more widespread, and other languages like python
> already provide
> support for them in there standard library.
>
> I hereby offer to take over maintenance of the SOAP::Lite module.
>
> My plans for SOAP::Lite maintenance are:
>
> 1) Work down the list of bug reports on CPAN & sourceforge
> 2) Split the SOAP/Lite.pm into separate files, while completely
> preserving SOAP::Lite's
> API
> In my opinion, the BIG SOAP/Lite.pm is one of the most serious
> design
> flaws in SOAP::Lite. This can easily be changed by moving to a
> one package/one file stragey.
> Separating packages into different files eases maintenance, and
> makes
> SOAP::Lite more "lightweight"
> 3) Factor out the seldomly used parts into separate packages.
> In my opinion, there's no need for Jabber or MQ support in SOAP-
> Lite -
> they could easily be factored out into SOAP-Lite-Jabber and SOAP-
> Lite-MQ
>
> distributions.
> I bet there's more to come...
> 4) Centralize contact.
> - move the yahoo groups user support forum to a user mailing list
> on sourceforge
> - move soaplite.com to soap-lite.sourceforge.net
>
> To introduce myself: I'm known on CPAN as MKUTTER. I'm the author
> of SOAP::WSDL,
> a WSDL-based frontend for SOAP::Lite. I'm currently doing a
> complete rewrite
> of SOAP::WSDL, and have learned - the hard way - that I can't use
> too much of
> SOAP::Lite as a base for SOAP::WSDL - actually, the only usable
> part is the
> transport backends.
>
> I'm also receiving user comments suggesting improvements which
> cannot be done
> without modifying SOAP::Lite, too.
>
> I consider this a very bad situation, which could be fixed easily -
> provided
> SOAP::Lite would be actively maintained.
>
> As there seems no one there to do the task, I'd just offer to do it
> myself.
>
>
> Regards,
>
> Martin
> * Gesendet mit / Sent by: FEN-Webmail * http://www.fen-net.de *
>
> ----------------------------------------------------------------------
> ---
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Soaplite-devel mailing list
> Soaplite-devel@...
> https://lists.sourceforge.net/lists/listinfo/soaplite-devel
>
|