qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <j...@apache.org>
Subject [jira] [Commented] (DISPATCH-1656) Allow user-configured connection properties in the Open performative
Date Thu, 28 May 2020 20:33:00 GMT

    [ https://issues.apache.org/jira/browse/DISPATCH-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119060#comment-17119060
] 

ASF subversion and git services commented on DISPATCH-1656:
-----------------------------------------------------------

Commit 0d2e54ee7c7f6baf440de8a123253916dfb34ed5 in qpid-dispatch's branch refs/heads/master
from Ken Giusti
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=0d2e54e ]

DISPATCH-1656: do not allow openProperties on connections to router


> Allow user-configured connection properties in the Open performative
> --------------------------------------------------------------------
>
>                 Key: DISPATCH-1656
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1656
>             Project: Qpid Dispatch
>          Issue Type: New Feature
>          Components: Router Node
>            Reporter: Ken Giusti
>            Assignee: Ken Giusti
>            Priority: Major
>             Fix For: 1.13.0
>
>
> This feature would add a new "openProperties" map attribute to the org.apache.qpid.dispatch.connector
and org.apache.qpid.dispatch.listener management entities. This new attribute is optional.
> The contents of the map are expected to be specified in JSON. The keys must be restricted
to ASCII characters only in order to be encoded as AMQP 1.0 Symbol types on the wire.
> Key values that start with the prefixes *qd.* or *x-opt-qd.* are reserved and must not
be used.
> In addition, the following keys are reserved and must not be used:
> product
>  version
>  failover-server-list
>  network-host
>  port
>  scheme
>  hostname
> The openProperties keys and values will be merged into the connection properties field
of the outgoing Open performative when establishing or accepting connections.
> The openProperties attribute is NOT allowed on connector or listener entities with roles
of either "inter-router" or "edge".
> The openProperties attribute is NOT allowed on listener entities than enable http, i.e.
http: true.
> Example:
> {{connector {}}
>  {{   name: broker}}
>  {{   role: route-container}}
>  {{   host: 127.0.0.1}}
>  {{   port: 22180}}
>  {{   saslMechanisms: ANONYMOUS}}
>  {{   *openProperties: {*}}
>  {{      *"foo": "bar",*}}
>  {{      *"integer": 7,*}}
>        {{*"list":  ["a", 1, "b", -9, true],*}}
>  {{*"map":  \{"key1": null, "key2": [1, 2, 3]\},*}}
>  {{*}*}}
>  {{   cost: 10}}
> {{}}}
> The resulting connection properties in the outgoing Open performative would include the
following map entries:
> {{Symbol(foo): String(bar),}}
> {{Symbol(integer): Int(7),}}
> {{Symbol(list): List(String(a), Int(1), String(b), Int(-9), Boolean),}}
> {{Symbol(map): Map(String(key1): Null, String(key2): List(Int(1), Int(2), Int(3)))}}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message