Provides the messaging system which monitors the connection in the underlying messaging system.
Namespace: Eneter.Messaging.MessagingSystems.Composites.MonitoredMessagingCompositAssembly: Eneter.Messaging.Framework (in Eneter.Messaging.Framework.dll) Version: 5.0.0.0 (5.0.0.0)
Syntax
| C# |
|---|
public class MonitoredMessagingFactory : IMessagingSystemFactory |
| Visual Basic |
|---|
Public Class MonitoredMessagingFactory _ Implements IMessagingSystemFactory |
| Visual C++ |
|---|
public ref class MonitoredMessagingFactory : IMessagingSystemFactory |
Remarks
When the connection is monitored, the duplex output channel periodically sends 'ping' messages
to the duplex input channel and waits for responses.
If the response comes within the specified timeout, the connection is open.
On the receiver side, the duplex input channel waits for the 'ping' messages and monitors if the connected duplex output channel is still alive. If the 'ping' message does not come within the specified timeout, the particular duplex output channel is disconnected.
Notice, the output channel and the input channel do not maintain an open connection. Therefore, the monitored messaging is not applicable for them. The implementation of this factory just uses the underlying messaging to create them.
Note Channels created by monitored messaging factory cannot communicate with channels, that were not created by monitored factory. E.g. the channel created with the monitored messaging factory with underlying TCP will not communicate with channels created directly with TCP messaging factory. The reason is, the communicating channels must understand the 'ping' communication.
On the receiver side, the duplex input channel waits for the 'ping' messages and monitors if the connected duplex output channel is still alive. If the 'ping' message does not come within the specified timeout, the particular duplex output channel is disconnected.
Notice, the output channel and the input channel do not maintain an open connection. Therefore, the monitored messaging is not applicable for them. The implementation of this factory just uses the underlying messaging to create them.
Note Channels created by monitored messaging factory cannot communicate with channels, that were not created by monitored factory. E.g. the channel created with the monitored messaging factory with underlying TCP will not communicate with channels created directly with TCP messaging factory. The reason is, the communicating channels must understand the 'ping' communication.
Inheritance Hierarchy
System..::..Object
Eneter.Messaging.MessagingSystems.Composites.MonitoredMessagingComposit..::..MonitoredMessagingFactory
Eneter.Messaging.MessagingSystems.Composites.MonitoredMessagingComposit..::..MonitoredMessagingFactory
