Message-ID: <460253378.298354.1368914065087.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_298353_434200612.1368914065087" ------=_Part_298353_434200612.1368914065087 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The LiveTribe :: SLP module is an implementation, writt= en in Java and deployable in any standard OSGi framework, of SLP, the Service Location Protocol.
The Service Location Protocol provides a scalable framework for the disc= overy and selection of network services.
Traditionally, users have had to find services by knowing the name of th= e host (or its network address). SLP eliminates the need for the user to kn= ow the name of the host that provides a service; rather, the user provides = the desired type of service and optional attributes that further describe t= he service, and SLP resolves the network address on behalf of the user.
SLP is useful in all those cases where you need to contact a remote serv= ice, but you don't know where it is located, or you don't know its JNDI nam= e.
Example: You want to contact an RMI server, but you don=
't know under which JNDI name the stub has been registered.
Example: You want to contact a JMXConnectorServer, but you= don't know its JMXServiceURL.
Example: You want to know how many JVMs there are in the n= etwork, but you don't know the exact number or host location.
Example: You want to automatically, with no additional pro= gramming, advertise a service URL when your OSGi service is registered and = automatically removed when the OSGi service is unregistered.
Example: You want to register OSGi service trackers to kee= p track of service URLs being registered on the network.
Example: You want to leverage OSGi's Configuration Admin S= ervice to configure SLP Service Agents and User Agents.