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

Andrew Stitcher commented on PROTON-1238:
-----------------------------------------

This issue per se isn't resolved so I'd just push it to 0.15.

I introduced operator<< for these objects (although I've not made sure that all 
API objects have the operator). But as I note above this is a "printable 
representation" not a "name".

It maybe that it is all that is required, but I'm not exactly sure at this 
point.

Adding a name API is a purely additive API change so can be introduced later 
without fear of messing up existing code.

I would open an issue with the C layer that the inspect results of many objects 
just give an object identifier (name) and not any indication of what's in the 
object (at a protocol level).

> 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.14.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.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to