Results 1,791–1,800 of 6,332 for /net-p2p/.(0.01 seconds)
Horde library for manipulating the Kolab user database
This package allows to read/write entries in the Kolab user database
stored in LDAP.
Horde library for managing an active Kolab session
This Horde package handles a Kolab session. It allows to authenticate
against LDAP and provides the users storage locations.
Open Source PBX and telephony toolkit
Asterisk is an Open Source PBX and telephony toolkit. It is, in a
sense, middleware between Internet and telephony channels on the bottom,
and Internet and telephony applications at the top.
Find out about running services
The What class is interface to classes providing information about running
services.
Horde Scribe client
Horde packaged version of the PHP Scribe client.
Handle X.500 DNs (Distinguished Names), parse, and format them
These modules handle X.500 DNs (Distinguished Names) and X.500 RDNs
(Relative Distinguished Names).
RFC: 2253
Exchange XML via AnyEvent::HTTP
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.
SOAP message messages with WSA fields
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
Fast and modular implementation for an XML-RPC client and server
Base-class for SOAP implementations
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.