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
you are dedicated to supporting the full SOAP API (not sure what SOAP::Lite
leaves out).
In that case, maybe you should call it Apache::SOAP::Lite rather than
Apache::SOAP
The benefit of breaking out Apache::SOAP(::Lite) into its own CPAN module
is that it will be easier for people to find your module. People who see
the APache::* module list and are looking for SOAP will say "Ah ha!" and
find out about your SOAP::Lite module and vice versa. It's like getting two
directory entries for the price of one. :)
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).
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 eventually
add drivers for these in the one package and presumably add SOAP Server
code that is shared amongst all the servers instead of breaking them out in
different packages.
Anyway, all I am saying is that in reply to your question about breaking
out Apache::SOAP is ...
"It depends".
And hopefully these comments will help you decide for yourself what you'd
like to do.
Thanks,
Gunther
At 12:42 PM 2/23/2001 -0800, Paul Kulchenko wrote:
>Apache::SOAP provides SOAP server functionality by simply adding
>couple of line in .htaccess or .conf file. Based on SOAP::Lite
>module, hence inherits all functionality, like, for example,
>compression on wire introduced in last version. For now released as
>part of SOAP::Lite module.
>Is there any value to ship it separately (probably as a mod_soap)?
>
>Module is available from www.soaplite.com or CPAN.
>
>Documentation and examples are included. Any comments are very
>welcome.
>
>Best wishes, Paul.
>
>=head1 NAME
>
>Apache::SOAP - Provide SOAP server functionality with simple
>configuration
>
>=head1 SYNOPSIS
>
>=over 4
>
>=item httpd.conf (Location), directory-based access
>
> <Location /mod_soap>
> SetHandler perl-script
> PerlHandler Apache::SOAP
> PerlSetVar dispatch_to "/Your/Path/To/Deployed/Modules,
>Module::Name, Module::method"
> PerlSetVar options "compress_threshold => 10000"
> </Location>
>
>=item httpd.conf (Files), file-based access
>
> <FilesMatch "\.soap$">
> SetHandler perl-script
> PerlHandler Apache::SOAP
> PerlSetVar dispatch_to "/Your/Path/To/Deployed/Modules,
>Module::Name, Module::method"
> PerlSetVar options "compress_threshold => 10000"
> </FilesMatch>
>
>=item .htaccess, directory-based access
>
> SetHandler perl-script
> PerlHandler Apache::SOAP
> PerlSetVar dispatch_to "/Your/Path/To/Deployed/Modules,
>Module::Name, Module::method"
> PerlSetVar options "compress_threshold => 10000"
>
>=back
>
>=head1 DESCRIPTION
>
>This Apache Perl module provides the ability to add support for SOAP
>(Simple
>Object Access Protocol) protocol with easy configuration (either
>in .conf or
>in .htaccess file). This functionality should give you lightweight
>option
>for hosting SOAP services and greatly simplify configuration aspects.
>
>This
>module inherites functionality from SOAP::Transport::HTTP::Apache
>component
>of SOAP::Lite module.
>
>=head1 CONFIGURATION
>
>The module can be placed in <Location>, <Directory>, <Files>,
><FilesMatch>
>directives in main server configuration areas or directly
>in .htaccess file.
>
>All parameters should be quoted and can be separated with commas or
>spaces
>for lists ("a, b, c") and with 'wide arrows' and commas for hash
>parameters
>("key1 => value1, key2 => value2").
>
>All options that you can find in SOAP::Transport::HTTP::Apache
>component
>are available for configuration. Here is the description of most
>important
>ones.
>
>=over 4
>
>=item dispatch_to (LIST)
>
>Specifies path to directory that contains Perl modules you'd like to
>give
>access to, or just list of modules (for preloaded modules).
>
> PerlSetVar dispatch_to "/Your/Path/To/Deployed/Modules,
>Module::Name, Module::method"
>
>=item options (HASH)
>
>Specifies list of options for your module, for example threshold for
>compression. Future versions will support more options. See
>SOAP::Transport::HTTP documentation for other options.
>
> PerlSetVar options "compress_threshold => 10000"
>
>=back
>
>=head1 DEPENDENCIES
>
> SOAP::Lite
> mod_perl
>
>=head1 SEE ALSO
>
> SOAP::Transport::HTTP::Apache for implementation details,
> SOAP::Lite for general information, and
> F<examples/server/mod_soap.htaccess> for .htaccess example
>
>=head1 COPYRIGHT
>
>Copyright (C) 2000-2001 Paul Kulchenko. All rights reserved.
>
>This library is free software; you can redistribute it and/or modify
>it under the same terms as Perl itself.
>
>=head1 AUTHOR
>
>Paul Kulchenko ([EMAIL PROTECTED])
>
>=cut
>
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! Auctions - Buy the things you want at great prices!
>http://auctions.yahoo.com/
__________________________________________________
Gunther Birznieks ([EMAIL PROTECTED])
eXtropia - The Web Technology Company
http://www.extropia.com/
