Endpoint instance to send requests to those communication endpoints. A ServerEndpoint instance contains the information necessary to listen for requests on the communication endpoints and to produce Endpoint instances. For example, a TCP-based ServerEndpoint implementation typically contains the TCP port to listen on and the host address to put in the Endpoint instances it produces. An implementation that supports authentication typically contains the {@link Subject}(if any) to use for server authentication.
The {@link #enumerateListenEndpoints enumerateListenEndpoints}method can be invoked to
ServerEndpoint, which are individually represented as {@link ListenEndpoint ListenEndpoint}instances, Endpoint instance that corresponds to the chosen listen operations Endpoint instance can then be used to send requests to the communication endpoints being listened on as a result of that {@link #enumerateListenEndpoints enumerateListenEndpoints} invocation.Typically, a ServerEndpoint is just used to specify the transport layer implementation to use when exporting a remote object; for example, some constructors of {@link BasicJeriExporter BasicJeriExporter} have a ServerEndpoint parameter tospecify the transport layer implementation. The exporter implementation is then responsible for using the supplied ServerEndpoint to manage listen operations as necessary and to obtain an Endpoint instance for putting in the client-side proxy.
All aspects of the underlying communication mechanism that are not specified here are defined by the particular implementation of this interface. @author Sun Microsystems, Inc. @since 2.0
| |