You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Andrew Stitcher (JIRA)" <ji...@apache.org> on 2017/12/11 19:00:03 UTC
[jira] [Created] (PROTON-1716) Consider whether container should be
navigable from the other objects
Andrew Stitcher created PROTON-1716:
---------------------------------------
Summary: Consider whether container should be navigable from the other objects
Key: PROTON-1716
URL: https://issues.apache.org/jira/browse/PROTON-1716
Project: Qpid Proton
Issue Type: Improvement
Components: cpp-binding
Reporter: Andrew Stitcher
Assignee: Cliff Jansen
The container is not really a necessary part of the C++ binding API - It partially exists as just a way to hold the container_id for the application.
An application written using the connection_driver API has no container and the only API difference is that trying to get the container out of connection_driver objects is an error.
Regular C++ binding API applications don't need the container object to be navigable - they could just store it in the on_container_start handler.
--
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