You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ted Ross (JIRA)" <ji...@apache.org> on 2011/02/17 18:27:24 UTC
[jira] Created: (QPID-3067) Example structure is misleading (c++
examples)
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:dev-subscribe@qpid.apache.org
[jira] Resolved: (QPID-3067) Example structure is misleading (c++
examples)
Posted by "Gordon Sim (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim resolved QPID-3067.
------------------------------
Resolution: Fixed
> 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
> Assignee: Gordon Sim
> 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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-3067) Example structure is misleading (c++
examples)
Posted by "Chuck Rolke (JIRA)" <ji...@apache.org>.
[ 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:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-3067) Example structure is misleading (c++
examples)
Posted by "Gordon Sim (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim reassigned QPID-3067:
--------------------------------
Assignee: Gordon Sim
> 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
> Assignee: Gordon Sim
> 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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-3067) Example structure is misleading (c++
examples)
Posted by "Carl Trieloff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996435#comment-12996435 ]
Carl Trieloff commented on QPID-3067:
-------------------------------------
When you do this, can you also bring william's example in jiri 2784
> 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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-3067) Example structure is misleading (c++
examples)
Posted by "Steve Huston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995955#comment-12995955 ]
Steve Huston commented on QPID-3067:
------------------------------------
That is a confusing aspect of the layout, I agree. Barring an effort to dissuade users from using old-api, I agree with this approach. If there's an effort to dissuade users, another option is to just remove the old-api examples.
> 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:dev-subscribe@qpid.apache.org