Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

apache::xmlrpc(3pm) [debian man page]

Apache::XMLRPC(3pm)					User Contributed Perl Documentation				       Apache::XMLRPC(3pm)

NAME
Apache::XMLRPC - serve XML-RPC requests from Apache SYNOPSIS
## ## Directives for your Apache config file. ## <Location /RPC2> SetHandler perl-script PerlHandler Apache::XMLRPC PerlSetVar XMLRPC_Config /usr/local/apache/xml-rpc/services </Location> ## ## In the 'services' file referenced above by 'XMLRPC_Config' ## sub foo { ... } sub bar { ... } $map = { foo => &foo, bar => &bar, }; 1; DESCRIPTION
Apache::XMLRPC serves Userland XML-RPC requests from Apache/mod_perl using the Frontier::RPC2 module. Configuring Apache::XMLRPC to work under mod_perl is a two step process. First, you must declare a "<Location>" directive in your Apache configuration file which tells Apache to use the content handler found in the Apache::XMLRPC module and defines a variable which tells the module where to find your services. Then, you must define the services. Apache Configuration Apache configuration is as simple as the "<Location>" directive shown in the synopsis above. Any directive allowed by Apache inside a "<Location>" block is allowed here, but the three lines shown above are required. Pay close attention to the 'PerlSetVar XMLRPC_Config ...' line as this is where you tell Apache where to find your services. This file may reside anywhere accessible by Apache. Defining Services To actually define the XML-RPC routines that will be served, they must reside in the file referenced by the 'PerlSetVar XMLRPC_Config ...' directive in the Apache configuration file. In this file you may place as many Perl subroutines as you like, but only those which are explicitly published will be available to your XML-RPC clients. To publish a subroutine, it must be included in the hash reference named $map (the hash reference must have this name as this is the variable that the Apache::XMLRPC passes to Frontier::RPC2::serve to actually service each request) The hash reference must be defined in this "services" file. The keys of the hash are the service names visible to the XML-RPC clients while the hash values are references to the subroutines you wish to make public. There is no requirement that the published service names match those of their associated subroutines, but it does make administration a little easier. SEE ALSO
perl(1), Frontier::RPC2(3) <http://www.scripting.com/frontier5/xml/code/rpc.html> AUTHOR
Ed Hill <ed-hill@uiowa.edu> is the original author. Tim Peoples <tep@colltech.com> added a few tweaks and all the documenation. perl v5.10.1 2011-04-05 Apache::XMLRPC(3pm)

Check Out this Related Man Page

Apache::SOAP(3) 					User Contributed Perl Documentation					   Apache::SOAP(3)

NAME
Apache::SOAP - mod_perl-based SOAP server with minimum configuration SYNOPSIS
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> 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> .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" 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. 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. 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" 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" METHODS
/SUBROUTINES server my $server = Apache::XMLRPC::Lite->server(); Returns the server object. Useful if you need to manipulate the server object from your code. handle Request handler. Called by apache. DEPENDENCIES
SOAP::Lite mod_perl SEE ALSO
SOAP::Transport::HTTP::Apache for implementation details, SOAP::Lite for general information, and F<examples/server/mod_soap.htaccess> for .htaccess example 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. AUTHOR
Paul Kulchenko (paulclinger@yahoo.com) perl v5.12.1 2010-03-17 Apache::SOAP(3)
Man Page