1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
2<html>
3    
4<head>
5<title></title>
6<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
7</head>    
8    
9<body>
10The kernel package is the heart of the JME networking module
11and controls the routing and dispatch of message data over
12different transport implementations.  Most users will never 
13have to deal with these classes unless they are writing their own 
14client and server implementations that diverge from the standard 
15classes that are provided.
16
17<p>{@link com.jme3.network.kernel.Kernel} defines the core of a server-side message
18broker that abstracts away the specific transport and underlying
19threading model used.  For example, it might use NIO selectors
20in a single threaded model or straight multithreaded socket
21model.  Or it might implement SSL connections.  Once created,
22{@link com.jme3.network.kernel.Kernel} users don't need to care about the details.</p>
23
24<p>{@link com.jme3.network.kernel.Endpoint} is a managed connection within a 
25{@link com.jme3.network.kernel.Kernel} providing kernel to client connectivity.</p>
26
27<p>{@link com.jme3.network.kernel.Connector} defines the basic client-side message sender
28and these objects are typically used to connect to a {@link com.jme3.network.kernel.Kernel} 
29though they can connect to any network port that supports the implementation's
30protocol.  Implementations are provided for straight TCP and UDP communication
31and could be extended to support SSL or different threading models.</p>  
32
33</body>
34</html>
35