Resoa Protocol Stack Implementation

Resoa Protocol Stack - Flexible, asynchronous P2P communication.

See:
Description

Most important packages

org.resoa.stack

The main package you need for working with the Resoa Stack.

Other Packages

org.resoa.stack.exception
org.resoa.stack.kernel	This package contains classes for internal use only.
org.resoa.stack.kernel.nio	This package contains classes for internal use only.
org.resoa.stack.kernel.tcp
org.resoa.stack.protocol	This package contains protocol specific stuff.
org.resoa.stack.protocol.impl	This package contains all stack protocols implementations The stack is initialized in the following order: MsgLength: Mandatory.
org.resoa.stack.protocol.service	This package contains classes for internal use only.
org.resoa.stack.protocol.service.impl
org.resoa.stack.security
org.resoa.stack.util

Resoa Protocol Stack - Flexible, asynchronous P2P communication.

Resoa Stack is a performance based, optimistic asynchronous communication solution using TCP/IP socket connections. Header structures are kept very small for achieving maximum bandwidth.

Features:

• channel / application domain based message categorization
• message prioritization, based on fragmentation with configurable size (default 8192 bytes)
• optional GZIP compression of each single message
• optional 128/256 bit AES encryption of each single message
• 1024/2048 bit public/private key authentication interface (RSA)
• optional digital signature. Each message might be wrapped by a XML, encrypting and signing the original content
• transaction request, commit and rollback support (this enables synchronous message handling)
• automatic reconnection by TCPClients,
• multiple Server IP addressing with random server selection. This allows client controlled load balancing strategies.
• Server side Java NIO / .net asynchronous socket/multi-threading architecture for high scalability of concurrent sessions

Overview of the underlying protocol stack

All non mandatory protocols can be activated for each single message.
The mandatory ProtocolActivation controls the individual activation during the stack processing.