[
https://issues.apache.org/activemq/browse/AMQNET-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46415#action_46415
]
Allan Schrum commented on AMQNET-26:
------------------------------------
OK, while waiting for comments, I have been looking at the Java
FailoverTransport() in greater detail. There is a level of detail in that
implementation that I do not think we can support (initially) for the C#
FailoverTransport(). For instance, the Java version tracks the current state of
a transaction so that it can try to replay all the commands (messages) so that
the transaction can be reprocessed on another connection. The necessary support
for this exists in the Java world, but not in our reduced interface world.
If I remember correctly, a message from the broker can be read and
automatically acknowledged, read and manually acknowledged, sent, or be part of
a transaction, or various connection failures. Failover capability can work in
each area only to a small amount.
For clarity, I am looking for a client state transition diagram (or will make
one) so that we can see how failover capability can respond in each state. From
that diagram I think it will be easier to determine what we can support.
> Add failover:// to NMS client
> -----------------------------
>
> Key: AMQNET-26
> URL: https://issues.apache.org/activemq/browse/AMQNET-26
> Project: ActiveMQ .Net
> Issue Type: New Feature
> Components: ActiveMQ Client
> Reporter: Denis Abramov
> Assignee: Jim Gomes
> Priority: Critical
> Fix For: 1.1
>
>
> Please add failover:// to C# NMS Client. I would add it but I don't know how
> to resume a stream once it is broken.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
