Helper to queue and process messages with a working thread.
Helper to write and read messages sfrom a stream.
Remote Procedure Calls (RPC).
Sending and receiving text messages.
Sending and receiving typed messages.
Attaching and detaching communication channels.
Communication with Android via the USB cable.
Extensions for messaging systems.
Extension providing client authentication.
Extension for automatic reconnect and buffering of sent messages in case the connection is not available.
Extension for communication via the message bus.
Extension providing monitoring the connection.
Encoding/decoding the communication between output and input channels.
Communication via HTTP.
Messaging system interfaces.
Synchronous communication within one process (like a synchronous local call).
Communication via TCP.
Communication routing messages into one working thread.
Asynchronous communication using multiple threads.
Communication via UDP.
Communication via Websockets.
Reducing communication via multiple channels into one channel.
Multiplying and forwarding of received messages.
Distributing the workload across a farm of receivers.
Receiving messages and events according to specified thread mode.
Helpers used by Eneter and which need to be API.
Welcome to the Eneter.Messaging.Framework, the cross-platform message oriented middleware.
Eneter Messaging Framework is a lightweight framework for the interprocess communication. It is easy to use and it works across multiple platforms.
The framework is available for various platforms. Therefore you can use it for the communication between applications from the same platform as well as for the communication between applications running on different platforms.
Communication across following platforms is supported:
The framework for Java and Android supports following protocols and transportation mechanisms:
Communicated messages are encoded by a serializer. To serialize/deserialize messages the framework for Java and Android supports:
The communication API is not bound to a particular protocol or encoding format, therefore your implementation stays same, does not matter what you use.
To implement the communication between applications the framework provides functionality to send and receive messages as well as the communication using RPC (Remote Procedure Calls):
It provides components to control routing of messages between applications:
The communication across the network is typically less reliable as a local call inside the process. The network connection can be interrupted or receiving application can be temporarily unavailable. If your communication scenario requires to overcome these issues, the framework provides:
The communication across the network is easy to observe and confidential data can be acquired by unauthorized persons. Therefore, you may want to protect your data:
Eneter Communication for Java and Android