[
https://issues.apache.org/jira/browse/ARTEMIS-2937?focusedWorklogId=504021&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-504021
]
ASF GitHub Bot logged work on ARTEMIS-2937:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Oct/20 05:14
Start Date: 23/Oct/20 05:14
Worklog Time Spent: 10m
Work Description: clebertsuconic edited a comment on pull request #3294:
URL: https://github.com/apache/activemq-artemis/pull/3294#issuecomment-714910747
the code with deliveryAnnotations re-encoding was already there before.. I
made things better now...
I actually had tried that before, and I tried today again, by making a
slight modification to use two links.. one for control and one for routing..
that way I won't need to use message annotation on control messages (I will
still need delivery annotations for messages though).
However having two links means having double flow control... and that was
the reason I didn't use two links before. I don't really want to mess with that
as things are working.
This is the reason why I selected a single link and using message
annotations over the control messages to not message with the body from the
client's application. I will leave it the way it is.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 504021)
Time Spent: 18h (was: 17h 50m)
> AMQP Server Connectivity
> ------------------------
>
> Key: ARTEMIS-2937
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2937
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: AMQP
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.16.0
>
> Time Spent: 18h
> Remaining Estimate: 0h
>
> This feature adds server side connectivity.
>
> It is possible to link two brokers directly using AMQP with this feature, and
> have a Queue transferring messages to another broker directly.
>
> For this we would have options called <sender and <receiver
>
>
> it would also be possible to use qpid-dispatch as an intermediary between
> clients and the brokers (or eventually between brokers), on that case the
> option will be <peer
>
> it would also be possible to use <mirror with a few option to replicate data
> between two brokers, bringing the possibility of using it for Disaster &
> Recovery and Failover.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
