Ports Search

Horde packaged version of the PHP Scribe client.

These modules handle X.500 DNs (Distinguished Names) and X.500 RDNs (Relative Distinguished Names). RFC: 2253

This module handles the exchange of (XML) messages, according to the rules of SOAP (any version). The module does not known how to parse or compose XML, but only worries about the HTTP aspects. In contrairy to XML::Compile::Transport::SOAPHTTP, this implementation can be used in various event-driven environments, via AnyEvent::HTTP.

The Web Service Addressing protocol is used to select certain service and port on a SOAP server, just like the "Host" header in "HTTP". The basic SOAP design uses the URI and the "soapAction" header of HTTP (in case it uses HTTP, by far the most often used transport mechanism) However, when the server is hidden behind firewalls and proxies, these fields are rewritten or replaced. This means that the definitions by the WSDL for the client can differ from the configuration of the

Fast and modular implementation for an XML-RPC client and server

This module handles the SOAP protocol. The first implementation is SOAP1.1 (http://www.w3.org/TR/2000/NOTE-SOAP-20000508/), which is still most often used. The SOAP1.2 definition (http://www.w3.org/TR/soap12/) is quite different; this module tries to define a sufficiently abstract interface to hide the protocol differences. Be aware that there are three kinds of SOAP: 1. Document style (literal) SOAP, where there is a WSDL file which explicitly types all out-going and incoming messages. Very easy to use. 2. RPC style SOAP literal. The WSDL file is not explicit about the content of the messages, but all messages must be schema defined types. 3. RPC style SOAP encoded. The sent data is nowhere described formally. The data is transported in some ad-hoc way.

XML::Compile::WSDL11 understands WSDL version 1.1. An WSDL file defines a set of messages to be send and received over (SOAP) connections. This involves encoding of the message to be send into XML, sending the message to the server, collect the answer, and finally decoding the XML to Perl. As end-user, you do not have to worry about the complex details of the messages and the way to exchange them: it's all simple Perl for you. Also, faults are handled automatically. The only complication you have to worry about is to shape a nested HASH structure to the sending message structure. XML::Compile::Schema::template() may help you. When the definitions are spread over multiple files you will need to use addWSDL() (wsdl) or importDefinitions() (additional schema's) explicitly. Usually, interreferences between those files are broken. Often they reference over networks (you should never trust). So, on purpose you must explicitly load the files you need from local disk! (of course, it is simple to find one-liners as work-arounds, but I will to tell you how!)

Pure Perl implementation for an XML-RPC client and server

XMLRPC::Lite is a collection of Perl modules which provides a simple interface to the XML-RPC Protocol (XML-RPC) both on client and server side. Based on SOAP::Lite module, it gives you access to all features and transports available in that module.

This class represents an XPC request or response.