Hi, Gunther!
--- Gunther Birznieks <[EMAIL PROTECTED]> wrote:
> Hmmm, I am under the impression that the DevelopMentor stuff has a
> mod_perl
> SOAP Handler (although I was never able to get it to work) so
> calling this
> one Apache::SOAP in the official name space seems a difficult sell
> unless
That's true, DM's SOAP module has mod_perl handler, but it's under
SOAP::Transport::HTTP::Apache namespace, and SOAP::Lite has also
Apache module under the same namespace, but it's just server
implementation, and Apache::SOAP's goal is to provide easy access to
implementation from configuration files (it is actually subclass of
SOAP::Transport::HTTP::Apache).
> you are dedicated to supporting the full SOAP API (not sure what
> SOAP::Lite leaves out).
First thing I did seven months ago was my email to Keith Brown
(author of DM's SOAP/Perl module) about possible ways for cooperation
and I'v been told that he's willing to, but design of his module
should be consistent with other DM's implementations and he has no
plans to change it. There was no easy way to combine our efforts and
I came up with another implementation. Don't want to praise myself,
but feature set seems to be pretty comparable with other toolkits. I
took ::Lite, just because SOAP namespace was already taken. It does
much more than you can expect from something with suffix Lite. "Lite
suffix reflects number of calories you should spend using this
module".
> In that case, maybe you should call it Apache::SOAP::Lite rather
> than Apache::SOAP
I thought about it, and in fact I released UDDI::Lite, but I also
plan to release DBD::SOAP, DBIx::SOAP and couple of other modules and
don't want to put suffix Lite everywhere, it could lead to confusion.
Also I don't think (IMHO) that DevelopMentor will ever support their
module, since they abandon SOAP development in Java, C++ and Perl and
there is no other SOAP modules in Perl and I don't have plans to stop
development any time soon. Moreover, I have a long TODO list :).
> find out about your SOAP::Lite module and vice versa. It's like
> getting two directory entries for the price of one. :)
Cool :)
> The annoying thing about breaking it out in its own module is that
> you
> might be tying Apache::SOAP tightly to the version of SOAP::Lite.
> If you
> consistently release new versions of both at the same time, then it
> will be
> a pain for people to constantly know they have two packages to
> download instead of one (although I guess it can be bundled).
Right, but there is no module specific code (it basically parameters
parsing), so I think I'll keep it inside SOAP::Lite for one more
version and then release as mod_soap.
> Another positive thing about keeping the bundle under SOAP::Lite is
> that
> you might consider releasing SOAP::Lite server code for other
> persistent
> engines like PerlEx, Velocigen, SpeedyCGI, etc... and you could
It works actually with Velocigen and as far as I understand with
PerlEx also, but I don't have any information about SpeedyCGI. It
also provides Daemon, TCP, CGI, IO, POP3 interfaces on server side
(in addition to mod_perl and Apache::Registry) as well as COM
interface and .... (hm, did I say already that I don't want to praise
myself?)
> And hopefully these comments will help you decide for yourself what
> you'd like to do.
Definitely, thanks a lot.
Best wishes, Paul.
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
