159b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 259b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta<html> 359b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta 459b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta<head> 559b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta<title></title> 659b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> 759b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta</head> 859b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta 959b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta<body> 1059b2e6871c65f58fdad78cd7229c292f6a177578Scott BartaThe kernel package is the heart of the JME networking module 1159b2e6871c65f58fdad78cd7229c292f6a177578Scott Bartaand controls the routing and dispatch of message data over 1259b2e6871c65f58fdad78cd7229c292f6a177578Scott Bartadifferent transport implementations. Most users will never 1359b2e6871c65f58fdad78cd7229c292f6a177578Scott Bartahave to deal with these classes unless they are writing their own 1459b2e6871c65f58fdad78cd7229c292f6a177578Scott Bartaclient and server implementations that diverge from the standard 1559b2e6871c65f58fdad78cd7229c292f6a177578Scott Bartaclasses that are provided. 1659b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta 1759b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta<p>{@link com.jme3.network.kernel.Kernel} defines the core of a server-side message 1859b2e6871c65f58fdad78cd7229c292f6a177578Scott Bartabroker that abstracts away the specific transport and underlying 1959b2e6871c65f58fdad78cd7229c292f6a177578Scott Bartathreading model used. For example, it might use NIO selectors 2059b2e6871c65f58fdad78cd7229c292f6a177578Scott Bartain a single threaded model or straight multithreaded socket 2159b2e6871c65f58fdad78cd7229c292f6a177578Scott Bartamodel. Or it might implement SSL connections. Once created, 2259b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta{@link com.jme3.network.kernel.Kernel} users don't need to care about the details.</p> 2359b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta 2459b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta<p>{@link com.jme3.network.kernel.Endpoint} is a managed connection within a 2559b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta{@link com.jme3.network.kernel.Kernel} providing kernel to client connectivity.</p> 2659b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta 2759b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta<p>{@link com.jme3.network.kernel.Connector} defines the basic client-side message sender 2859b2e6871c65f58fdad78cd7229c292f6a177578Scott Bartaand these objects are typically used to connect to a {@link com.jme3.network.kernel.Kernel} 2959b2e6871c65f58fdad78cd7229c292f6a177578Scott Bartathough they can connect to any network port that supports the implementation's 3059b2e6871c65f58fdad78cd7229c292f6a177578Scott Bartaprotocol. Implementations are provided for straight TCP and UDP communication 3159b2e6871c65f58fdad78cd7229c292f6a177578Scott Bartaand could be extended to support SSL or different threading models.</p> 3259b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta 3359b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta</body> 3459b2e6871c65f58fdad78cd7229c292f6a177578Scott Barta</html> 35