[
https://issues.apache.org/jira/browse/QPID-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995979#comment-12995979
]
Chuck Rolke commented on QPID-3067:
-----------------------------------
Move them to old-api and don't delete them.
Although you are discouraging its use, the old api it is still used
significantly by WCF.
You can dissuade new users by moving the offending examples to an old-api
directory. Also, rename the old-api projects in CMake with an "old-api-"
prefix. That way, under a visual studio solution, the examples would be grouped
together in Solution Explorer and the user is alerted that they use an old api.
If ever you change the client library interface then the old-api examples may
prove useful still by exposing the changes.
> Example structure is misleading (c++ examples)
> ----------------------------------------------
>
> Key: QPID-3067
> URL: https://issues.apache.org/jira/browse/QPID-3067
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Client, Qpid Examples
> Affects Versions: 0.8
> Reporter: Ted Ross
> Fix For: 0.9
>
>
> The structure of the examples directory (as installed) is the following:
> direct
> failover
> fanout
> messaging
> pub-sub
> qmf-console
> request-response
> tradedemo
> verify
> verify_all
> xml-exchange
> This structure hides the fact that there are two APIs, an old one and a new,
> recommended API. The uninitiated are not going to figure out that they
> should be looking in the "messaging" directory for the most relevant examples.
> I'd like to suggest that we rearrange these directories such that all old-API
> examples are under a single subdirectory called "old-api" or similar.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
