[
https://issues.apache.org/jira/browse/DISPATCH-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186583#comment-17186583
]
Robbie Gemmell commented on DISPATCH-1765:
------------------------------------------
Right, so I'm saying 1.14.0 wouldn't use the feature against 1.13.0 if you
moved to capabilities based detection, unless it were special-cased to still
detect 1.13.0 as it does now. How much of an annoyance that is might depend on
when 1.14.0 actually happens; if really soon, perhaps not of concern..if later
when folks have 1.13.0 deployed, perhaps annoying.
> Router version parsing is broken
> --------------------------------
>
> Key: DISPATCH-1765
> URL: https://issues.apache.org/jira/browse/DISPATCH-1765
> Project: Qpid Dispatch
> Issue Type: Bug
> Affects Versions: 1.13.0
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Priority: Major
> Fix For: 1.14.0
>
>
> The version string advertised by the router in the Open performative may be
> parsed incorrectly if a non-semantic format is used (e.g. a git commit sha).
> Currently the router uses the router version of its peer in order to
> determine if the peer supports certain features like streaming links.
> Two changes proposed to solve this:
> 1) do not attempt to parse the version string arriving in the Open
> performative. Treat it as opaque ascii data.
> 2) Add router-defined capabilities and advertise them in the
> offered-capabilities field of the Open performative.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
