[
https://issues.apache.org/jira/browse/DISPATCH-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359222#comment-14359222
]
ASF subversion and git services commented on DISPATCH-98:
---------------------------------------------------------
Commit 1666279 from [~kgiusti] in branch 'dispatch/trunk'
[ https://svn.apache.org/r1666279 ]
DISPATCH-98: Refactor message annotation handling
Allows the various annotations to be set on a per-message basis.
> Refactor the handling of Message Annotations
> --------------------------------------------
>
> Key: DISPATCH-98
> URL: https://issues.apache.org/jira/browse/DISPATCH-98
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Router Node
> Affects Versions: 0.3
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Priority: Minor
> Fix For: 0.5
>
>
> In order to facility DISPATCH-89, we need to modify the way the router
> updates the router-specific fields in the Message Annotations section of a
> forwarded message.
> Currently, all the salient fields - trace, ingress, to-override, etc - are
> updated all at once prior to forwarding. Let's break this up so fields may
> be updated individually as needed. Specifically, for DISPATCH-89, the custom
> forwarding code will need to update the to-override after the route lookup is
> done. In addition, will need to set unique values for to-override for each
> copy of the message that is created.
> As an optimization, we should adopt a lazy approach to encoding these field
> values: only build the final outgoing Message Annotation section as the
> message is being sent out.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
