Eneter Messaging Framework is a lightweight framework for the interprocess communication. It is easy to use and it works across various platforms. The framework provides communication components that can be used to create communication scenarios fitting your needs.
Supported Platforms
The framework is available for multiple platforms. Therefore, you can use it for communication between two Java applications but also for the communication between Java, Android and .NET applications.
The framework is available for:
- Java 6
- Android 2.1 (or later)
- .NET 3.5, .NET 4.0, .NET 4.5
- Windows Phone 7, Windows Phone 7.1
- Silverlight 3, Silverlight 4, Silverlight 5
- Mono 2.6.4
Protocols
The framework for Java and Android supports following protocols and transportation mechanisms:
- TCP - for communication between processes running on different machines.
- Websocket - for communication between processes running on different machines. It provides true bi-directional, full-duplex communication in environments which block non-standard Internet connections using a firewall.
- HTTP - for communication between processes running on different machines. It works in environments blocking non-standard Internet connections using a firewall.
- Android USB Cable - for communication between computer and Android device connected via the USB cable.
- Thread Messaging - for communication between threads running in the same process.
Message Serialization
Communicated messages are encoded by a serializer. To serialize/deserialize messages the framework supports:
- XML Serializer - serialization to XML (works for the communication between Java and .NET).
- Binary Serializer - for fast serialization using the binary format (does not work for the communication between Java and .NET).
- AES Serializer - for encrypting using Advanced Encryption Standard (works for the communication between Java and .NET).
- GZip Serializer - for compressing big messages before sending across the network (works for the communication between Java and .NET).
- RSA Serializer - for encrypting messages by RSA algorithm using public and private keys (works for the communication between Java and .NET).
- RSA Digitally Signing Serializer - for using digital signature to verify who sent the message and that the message was not changed (works for the communication between Java and .NET).
The communication API is not bound to a particular protocol or encoding format, therefore your implementation stays same, does not matter what you use.
Sending-Receiving Messages
To implement the communication between applications, the framework provides functionality to send and receive messages. Communication can be one-way or request-response and messages can be:
- String Messages - for sending and receiving text messages.
- Typed Messages - for sending and receiving data structures of specified types.
Routing Messages
It provides components that can be placed on the communication path to control the routing behavior.
- Broker - for publish-subscribe scenarios (publisher sends messages to the broker and the broker notifies all subscribers).
- Dispatcher - for routing messages to all connected receivers (e.g. for a service listening to TCP and HTTP at the same time).
- Channel Wrapper/Unwrapper - for receiving multiple type of messages on one address (no need for if ... else ... statement in the user code).
- Load Balancer - for distributing workload across more computers (or processes).
Reliability
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:
- Monitoring of connection availability - for early detection of a disconnection.
- Buffered messaging and automatic reconnect - for overcoming short disconnections (e.g. in case of unstable network).
- Acknowledged messaging - for getting notification whether a message was delivered or not.
Security
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:
- SSL or serializer using a cryptographic algorithm AES, RSA or RSA based digital signature.
Eneter Communication
| Packages | |
|---|---|
| eneter.messaging.dataprocessing.messagequeueing | The package contains the supporting functionality for queuing and processing messages with the working thread. |
| eneter.messaging.dataprocessing.serializing | Functionality to serialize and deserialize messages or data. |
| eneter.messaging.diagnostic | Functionality for tracing and debugging purposes. |
| eneter.messaging.endpoints.stringmessages | Functionality to send and receive simple text messages. |
| eneter.messaging.endpoints.typedmessages | Sending and receiving messages as typed data. |
| eneter.messaging.infrastructure.attachable | Interfaces used by components to be able to attach channels. |
| eneter.messaging.messagingsystems.androidusbcablemessagingsystem | The messaging system transferring messages between Android and computer via USB cable. |
| eneter.messaging.messagingsystems.composites | Functionality extending the default behavior of messaging systems. |
| eneter.messaging.messagingsystems.composites.bufferedmessagingcomposit | Provides the messaging system which buffers sent messages if the connection is not available. |
| eneter.messaging.messagingsystems.composites.monitoredmessagingcomposit | Monitoring the connection between communicating applications. |
| eneter.messaging.messagingsystems.connectionprotocols | Functionality for encoding/decoding the low-level communication between communicating channels. |
| eneter.messaging.messagingsystems.httpmessagingsystem | The messaging system transferring messages via HTTP. |
| eneter.messaging.messagingsystems.messagingsystembase | Interfaces representing the messaging system. |
| eneter.messaging.messagingsystems.synchronousmessagingsystem | The messaging system transferring messages synchronously in the context of the caller thread. |
| eneter.messaging.messagingsystems.tcpmessagingsystem | The messaging system transferring messages via TCP. |
| eneter.messaging.messagingsystems.threadmessagingsystem | The messaging system transferring messages between threads by using the working thread processing messages from the queue. |
| eneter.messaging.messagingsystems.threadpoolmessagingsystem | The messaging system transfering messages between threads by using the thread pool. |
| eneter.messaging.messagingsystems.websocketmessagingsystem | The messaging system transferring messages via websockets. |
| eneter.messaging.nodes.broker | Functionality for publish-subscribe scenarios. |
| eneter.messaging.nodes.channelwrapper | Functionality for sending/receiving more message types via one channel. |
| eneter.messaging.nodes.dispatcher | Functionality for the component forwarding messages to all attached receivers. |
| eneter.messaging.nodes.loadbalancer | Functionality to distribute the workload across a farm of receivers. |
| eneter.net.system | Helpers simulating some functionality from .NET. |
|
||||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||