You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ken Giusti (JIRA)" <ji...@apache.org> on 2015/01/15 20:56:34 UTC
[jira] [Created] (DISPATCH-98) Refactor the handling of Message
Annotations
Ken Giusti created DISPATCH-98:
----------------------------------
Summary: 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
Priority: Minor
Fix For: 0.4
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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org