Uses of Package
com.hazelcast.internal.networking

Packages that use com.hazelcast.internal.networking

Package	Description
com.hazelcast.client	Contains classes/interfaces related to Client
com.hazelcast.client.connection.nio	Contains classes related to New IO for com.hazelcast.client.connection
com.hazelcast.client.impl	Contains most of the client side HazelcastInstance implementation functionality.
com.hazelcast.client.impl.protocol	Client protocol related private implementation classes
com.hazelcast.client.impl.protocol.util	Protocol utils
com.hazelcast.instance	This package contains Hazelcast Instance functionality.
com.hazelcast.internal.ascii	This package contains Ascii functionality for Hazelcast. This is required for Memcached and the REST api.
com.hazelcast.internal.ascii.memcache	This package contains MemoryCache functionality for Hazelcast.
com.hazelcast.internal.ascii.rest	This package contains Reset functionality for Hazelcast.
com.hazelcast.internal.diagnostics	Contains functionality what is happening in a HazelcastInstance.
com.hazelcast.internal.networking	Contains the socket connection functionality.
com.hazelcast.internal.networking.nio	Contains the non blocking EventLoopGroup functionality.
com.hazelcast.internal.networking.spinning	Contains the implementation of the SpinningEventLoopGroup.
com.hazelcast.nio	This package contains classes related to New IO
com.hazelcast.nio.ascii	Contains SocketTextReader and SocketTextWriter classes;
com.hazelcast.nio.tcp	Contains functionality for the TCP/IP Networking for cluster members This whole package is internal and no compatibility will be provided.

Classes in com.hazelcast.internal.networking used by com.hazelcast.client

Class and Description
ChannelFactory A factory for creating Channel instances.

Classes in com.hazelcast.internal.networking used by com.hazelcast.client.connection.nio

Class and Description
Channel A Channel is a construct that can send/receive like Packets/ClientMessages etc.
OutboundFrame Represents something that can be written to a Channel There are different types of OutboundFrame: Packet: for member to member and old-client to member communication TextMessage: for memcached and rest communication ClientMessage: for the new client to member communication Till so far, all communication over a single connection, will be of a single Frame-class.

Classes in com.hazelcast.internal.networking used by com.hazelcast.client.impl

Class and Description
ChannelFactory A factory for creating Channel instances.

Classes in com.hazelcast.internal.networking used by com.hazelcast.client.impl.protocol

Class and Description
OutboundFrame Represents something that can be written to a Channel There are different types of OutboundFrame: Packet: for member to member and old-client to member communication TextMessage: for memcached and rest communication ClientMessage: for the new client to member communication Till so far, all communication over a single connection, will be of a single Frame-class.

Classes in com.hazelcast.internal.networking used by com.hazelcast.client.impl.protocol.util

Class and Description
ChannelInboundHandler The ChannelInboundHandler provides control when data is received and needs to be processed.

Classes in com.hazelcast.internal.networking used by com.hazelcast.instance

Class and Description
ChannelFactory A factory for creating Channel instances.
ChannelInboundHandler The ChannelInboundHandler provides control when data is received and needs to be processed.
ChannelOutboundHandler Responsible for writing OutboundFrame to a ByteBuffer.

Classes in com.hazelcast.internal.networking used by com.hazelcast.internal.ascii

Class and Description
OutboundFrame Represents something that can be written to a Channel There are different types of OutboundFrame: Packet: for member to member and old-client to member communication TextMessage: for memcached and rest communication ClientMessage: for the new client to member communication Till so far, all communication over a single connection, will be of a single Frame-class.

Classes in com.hazelcast.internal.networking used by com.hazelcast.internal.ascii.memcache

Class and Description
OutboundFrame Represents something that can be written to a Channel There are different types of OutboundFrame: Packet: for member to member and old-client to member communication TextMessage: for memcached and rest communication ClientMessage: for the new client to member communication Till so far, all communication over a single connection, will be of a single Frame-class.

Classes in com.hazelcast.internal.networking used by com.hazelcast.internal.ascii.rest

Class and Description
OutboundFrame Represents something that can be written to a Channel There are different types of OutboundFrame: Packet: for member to member and old-client to member communication TextMessage: for memcached and rest communication ClientMessage: for the new client to member communication Till so far, all communication over a single connection, will be of a single Frame-class.

Classes in com.hazelcast.internal.networking used by com.hazelcast.internal.diagnostics

Class and Description
EventLoopGroup The EventLoopGroup is responsible for processing registered channels.

Classes in com.hazelcast.internal.networking used by com.hazelcast.internal.networking

Class and Description
Channel A Channel is a construct that can send/receive like Packets/ClientMessages etc.
ChannelCloseListener A listener called when a Channel is closed.
ChannelInboundHandler The ChannelInboundHandler provides control when data is received and needs to be processed.
ChannelOutboundHandler Responsible for writing OutboundFrame to a ByteBuffer.
InitResult
OutboundFrame Represents something that can be written to a Channel There are different types of OutboundFrame: Packet: for member to member and old-client to member communication TextMessage: for memcached and rest communication ClientMessage: for the new client to member communication Till so far, all communication over a single connection, will be of a single Frame-class.

Classes in com.hazelcast.internal.networking used by com.hazelcast.internal.networking.nio

Class and Description
AbstractChannel An abstract Channel implementation.
Channel A Channel is a construct that can send/receive like Packets/ClientMessages etc.
ChannelErrorHandler A strategy for controlling what needs to be done in case of an Exception being thrown when the EventLoopGroup processes events.
ChannelFactory A factory for creating Channel instances.
ChannelInboundHandler The ChannelInboundHandler provides control when data is received and needs to be processed.
ChannelInitializer Initializes the Channel when the Channel is used for the first time.
EventLoopGroup The EventLoopGroup is responsible for processing registered channels.
OutboundFrame Represents something that can be written to a Channel There are different types of OutboundFrame: Packet: for member to member and old-client to member communication TextMessage: for memcached and rest communication ClientMessage: for the new client to member communication Till so far, all communication over a single connection, will be of a single Frame-class.

Classes in com.hazelcast.internal.networking used by com.hazelcast.internal.networking.spinning

Class and Description
AbstractChannel An abstract Channel implementation.
Channel A Channel is a construct that can send/receive like Packets/ClientMessages etc.
ChannelErrorHandler A strategy for controlling what needs to be done in case of an Exception being thrown when the EventLoopGroup processes events.
ChannelFactory A factory for creating Channel instances.
ChannelInitializer Initializes the Channel when the Channel is used for the first time.
EventLoopGroup The EventLoopGroup is responsible for processing registered channels.
OutboundFrame Represents something that can be written to a Channel There are different types of OutboundFrame: Packet: for member to member and old-client to member communication TextMessage: for memcached and rest communication ClientMessage: for the new client to member communication Till so far, all communication over a single connection, will be of a single Frame-class.

Classes in com.hazelcast.internal.networking used by com.hazelcast.nio

Class and Description
ChannelFactory A factory for creating Channel instances.
ChannelInboundHandler The ChannelInboundHandler provides control when data is received and needs to be processed.
ChannelOutboundHandler Responsible for writing OutboundFrame to a ByteBuffer.
OutboundFrame Represents something that can be written to a Channel There are different types of OutboundFrame: Packet: for member to member and old-client to member communication TextMessage: for memcached and rest communication ClientMessage: for the new client to member communication Till so far, all communication over a single connection, will be of a single Frame-class.

Classes in com.hazelcast.internal.networking used by com.hazelcast.nio.ascii

Class and Description
ChannelInboundHandler The ChannelInboundHandler provides control when data is received and needs to be processed.
ChannelOutboundHandler Responsible for writing OutboundFrame to a ByteBuffer.

Classes in com.hazelcast.internal.networking used by com.hazelcast.nio.tcp

Class and Description
Channel A Channel is a construct that can send/receive like Packets/ClientMessages etc.
ChannelErrorHandler A strategy for controlling what needs to be done in case of an Exception being thrown when the EventLoopGroup processes events.
ChannelInboundHandler The ChannelInboundHandler provides control when data is received and needs to be processed.
ChannelInitializer Initializes the Channel when the Channel is used for the first time.
ChannelOutboundHandler Responsible for writing OutboundFrame to a ByteBuffer.
EventLoopGroup The EventLoopGroup is responsible for processing registered channels.
InitResult
OutboundFrame Represents something that can be written to a Channel There are different types of OutboundFrame: Packet: for member to member and old-client to member communication TextMessage: for memcached and rest communication ClientMessage: for the new client to member communication Till so far, all communication over a single connection, will be of a single Frame-class.