You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <qp...@incubator.apache.org> on 2007/10/26 22:49:50 UTC

[jira] Created: (QPID-664) High-level C++ client API.

High-level C++ client API.
--------------------------

                 Key: QPID-664
                 URL: https://issues.apache.org/jira/browse/QPID-664
             Project: Qpid
          Issue Type: Bug
          Components: C++ Client
            Reporter: Alan Conway


Attached a proposal for a high-level C++ client API. The existing client::Session class will be renamed Session_0_10 and remain as an internal direct mapping of the 0_10 protocol. The new API is just a thin layer over Session_0_10 providing:
 - improved usability
 - abstraction from specific protocol version

The usability improvements include
 - Self-contained classes reflecting domain concepts (Queue, Exchange, Subscriber, Subscription)
 - simplification of obscure (and probably change-prone protocol) areas: E.g. apply a simple flow control policy object rather than fiddling with session.MessageFlow functions.
 - Better memory safety, simpler thread management (these last points could be integrated early into the existing API.)

Comments are most welcome, lets hone it before we implement it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (QPID-664) High-level C++ client API.

Posted by "Alan Conway (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Conway updated QPID-664:
-----------------------------

    Attachment: CppClientApi.cpp

> High-level C++ client API.
> --------------------------
>
>                 Key: QPID-664
>                 URL: https://issues.apache.org/jira/browse/QPID-664
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Client
>            Reporter: Alan Conway
>         Attachments: CppClientApi.cpp
>
>
> Attached a proposal for a high-level C++ client API. The existing client::Session class will be renamed Session_0_10 and remain as an internal direct mapping of the 0_10 protocol. The new API is just a thin layer over Session_0_10 providing:
>  - improved usability
>  - abstraction from specific protocol version
> The usability improvements include
>  - Self-contained classes reflecting domain concepts (Queue, Exchange, Subscriber, Subscription)
>  - simplification of obscure (and probably change-prone protocol) areas: E.g. apply a simple flow control policy object rather than fiddling with session.MessageFlow functions.
>  - Better memory safety, simpler thread management (these last points could be integrated early into the existing API.)
> Comments are most welcome, lets hone it before we implement it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (QPID-664) High-level C++ client API.

Posted by "Gordon Sim (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gordon Sim reassigned QPID-664:
-------------------------------

    Assignee: Gordon Sim

> High-level C++ client API.
> --------------------------
>
>                 Key: QPID-664
>                 URL: https://issues.apache.org/jira/browse/QPID-664
>             Project: Qpid
>          Issue Type: New Feature
>          Components: C++ Client
>            Reporter: Alan Conway
>            Assignee: Gordon Sim
>         Attachments: CppClientApi.cpp
>
>
> Attached a proposal for a high-level C++ client API. The existing client::Session class will be renamed Session_0_10 and remain as an internal direct mapping of the 0_10 protocol. The new API is just a thin layer over Session_0_10 providing:
>  - improved usability
>  - abstraction from specific protocol version
> The usability improvements include
>  - Self-contained classes reflecting domain concepts (Queue, Exchange, Subscriber, Subscription)
>  - simplification of obscure (and probably change-prone protocol) areas: E.g. apply a simple flow control policy object rather than fiddling with session.MessageFlow functions.
>  - Better memory safety, simpler thread management (these last points could be integrated early into the existing API.)
> Comments are most welcome, lets hone it before we implement it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


[jira] Updated: (QPID-664) High-level C++ client API.

Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marnie McCormack updated QPID-664:
----------------------------------

    Fix Version/s:     (was: M4)

> High-level C++ client API.
> --------------------------
>
>                 Key: QPID-664
>                 URL: https://issues.apache.org/jira/browse/QPID-664
>             Project: Qpid
>          Issue Type: New Feature
>          Components: C++ Client
>            Reporter: Alan Conway
>         Attachments: CppClientApi.cpp
>
>
> Attached a proposal for a high-level C++ client API. The existing client::Session class will be renamed Session_0_10 and remain as an internal direct mapping of the 0_10 protocol. The new API is just a thin layer over Session_0_10 providing:
>  - improved usability
>  - abstraction from specific protocol version
> The usability improvements include
>  - Self-contained classes reflecting domain concepts (Queue, Exchange, Subscriber, Subscription)
>  - simplification of obscure (and probably change-prone protocol) areas: E.g. apply a simple flow control policy object rather than fiddling with session.MessageFlow functions.
>  - Better memory safety, simpler thread management (these last points could be integrated early into the existing API.)
> Comments are most welcome, lets hone it before we implement it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (QPID-664) High-level C++ client API.

Posted by "Rafael H. Schloming (JIRA)" <qp...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/QPID-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538554 ] 

Rafael H. Schloming commented on QPID-664:
------------------------------------------

How specific do you think this is to C++? Do you have any interest in documenting this as a cross language API guideline?

> High-level C++ client API.
> --------------------------
>
>                 Key: QPID-664
>                 URL: https://issues.apache.org/jira/browse/QPID-664
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Client
>            Reporter: Alan Conway
>         Attachments: CppClientApi.cpp
>
>
> Attached a proposal for a high-level C++ client API. The existing client::Session class will be renamed Session_0_10 and remain as an internal direct mapping of the 0_10 protocol. The new API is just a thin layer over Session_0_10 providing:
>  - improved usability
>  - abstraction from specific protocol version
> The usability improvements include
>  - Self-contained classes reflecting domain concepts (Queue, Exchange, Subscriber, Subscription)
>  - simplification of obscure (and probably change-prone protocol) areas: E.g. apply a simple flow control policy object rather than fiddling with session.MessageFlow functions.
>  - Better memory safety, simpler thread management (these last points could be integrated early into the existing API.)
> Comments are most welcome, lets hone it before we implement it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (QPID-664) High-level C++ client API.

Posted by "Gordon Sim (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gordon Sim updated QPID-664:
----------------------------

    Issue Type: New Feature  (was: Bug)

> High-level C++ client API.
> --------------------------
>
>                 Key: QPID-664
>                 URL: https://issues.apache.org/jira/browse/QPID-664
>             Project: Qpid
>          Issue Type: New Feature
>          Components: C++ Client
>            Reporter: Alan Conway
>             Fix For: M4
>
>         Attachments: CppClientApi.cpp
>
>
> Attached a proposal for a high-level C++ client API. The existing client::Session class will be renamed Session_0_10 and remain as an internal direct mapping of the 0_10 protocol. The new API is just a thin layer over Session_0_10 providing:
>  - improved usability
>  - abstraction from specific protocol version
> The usability improvements include
>  - Self-contained classes reflecting domain concepts (Queue, Exchange, Subscriber, Subscription)
>  - simplification of obscure (and probably change-prone protocol) areas: E.g. apply a simple flow control policy object rather than fiddling with session.MessageFlow functions.
>  - Better memory safety, simpler thread management (these last points could be integrated early into the existing API.)
> Comments are most welcome, lets hone it before we implement it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.