You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2017/07/19 19:26:00 UTC
[jira] [Updated] (PROTON-1238) proton::connection objects (and
others too) don't have useful names
[ https://issues.apache.org/jira/browse/PROTON-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Ross updated PROTON-1238:
--------------------------------
Fix Version/s: (was: 0.18.0)
0.19.0
> proton::connection objects (and others too) don't have useful names
> -------------------------------------------------------------------
>
> Key: PROTON-1238
> URL: https://issues.apache.org/jira/browse/PROTON-1238
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Fix For: 0.19.0
>
>
> [Issue "reimagined" to fit the actual use case.]
> If you want to report to the user and refer to a connection (and probably other proton objects) there is no easy way to get a unique name that we can use to refer to a connection.
> The name is distinct from the url used to create the connection (although url would work as a name). The name is also distinct from a printable representation of the object.
> Originally the issue was:
> Although the user could just remember whatever url they used to create a given connection, it is duplicative when the library has the info around.
> Also if it is not provided then the user has to plumb to info to places it is needed inside the event handlers, however the handlers will already get the connection context object anyway so that is unecessary and an extra burden.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org