net.jini.discovery.https discovery
format.See: Description
| Class | Description |
|---|---|
| DiscoveryUnicastHTTPS |
This exists as a separate https protocol because the jini discovery protocol
cannot perform the required handshake negotiation to select a provider
as specified in DJ.2.6.6 and DJ.2.6.7 through firewalls and https proxy servers.
|
net.jini.discovery.https discovery
format. This is not an implementation of the jini:// unicast discovery protocol.
This is a direct connection to a registrar using a unicast https:// connection.
This implementation doesn't implement either Discovery protocols, v1 or v2.
The unicast response data sent by the lookup service, is in the following form:
The table below illustrates the layout for unicast response discovery format data specified by the net.jini.discovery.plaintext discovery format. The values to encode are described in Section DJ.2.6.3, "Unicast Response Contents".
The discovery format data consists of a contiguous series of values in the order listed above from top to bottom. Values of type String are encoded in the format specified for the writeUTF method of the java.io.DataOutput interface. Unsigned short values are encoded as if they were cast to signed short values, and then written in the format specified for the writeShort method of the java.io.DataOutput interface. The registrar proxy is written in the same format that would be produced by constructing a java.io.ObjectOutputStream, and writing to it an instance of net.jini.io.MarshalledInstance containing the marshalled registrar proxy. The number of group strings written must be equal to the group count value.
net.jini.jeri.ssl package.
net.jini.jeri.ssl package.Copyright © 2016–2018. All rights reserved.