Package com.jme3.network.kernel

The kernel package is the heart of the JME networking module and controls the routing and dispatch of message data over different transport implementations.

See:
          Description

Interface Summary
Connector A single channel remote connection allowing the sending and receiving of data.
Endpoint An abstract endpoint in a Kernel that can be used for sending/receiving messages within the kernel space.
Kernel Defines the basic byte[] passing messaging kernel.
 

Class Summary
AbstractKernel Base implementation of the Kernel interface providing several useful default implementations of some methods.
EndpointEvent Provides information about an added or removed connection.
Envelope Encapsulates a received piece of data.
NamedThreadFactory A simple factory that delegates to java.util.concurrent's default thread factory but adds a prefix to the beginning of the thread name.
 

Enum Summary
EndpointEvent.Type  
 

Exception Summary
ConnectorException Represents a client-side connection error, usually encapsulating an IOException as its cause.
KernelException Represents a kernel-level error, usually encapsulating an IOException as its cause.
 

Package com.jme3.network.kernel Description

The kernel package is the heart of the JME networking module and controls the routing and dispatch of message data over different transport implementations. Most users will never have to deal with these classes unless they are writing their own client and server implementations that diverge from the standard classes that are provided.

Kernel defines the core of a server-side message broker that abstracts away the specific transport and underlying threading model used. For example, it might use NIO selectors in a single threaded model or straight multithreaded socket model. Or it might implement SSL connections. Once created, Kernel users don't need to care about the details.

Endpoint is a managed connection within a Kernel providing kernel to client connectivity.

Connector defines the basic client-side message sender and these objects are typically used to connect to a Kernel though they can connect to any network port that supports the implementation's protocol. Implementations are provided for straight TCP and UDP communication and could be extended to support SSL or different threading models.