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

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

I've added operator<< for wrapped proton-c objects and this should allow a 
printable representation of the wrapped objects to be generated. However the 
underlying proton-c object inspect functionality is underwhelming! It merely 
gives (in these cases) the object type and and address.
It probably the correct way to this, but we should improve the underlying 
proton-c inspect for these objects.

> 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