[
https://issues.apache.org/jira/browse/QPID-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872143#action_12872143
]
Gordon Sim commented on QPID-2628:
----------------------------------
I think it would be clearer to keep QPID-2589 for improvements to the core
binding, and restrict this Jira to the stated scope i.e. consideration of
dispatching received messages to a callback.
> c++ messaging API dotnet binding needs received message callback
> ----------------------------------------------------------------
>
> Key: QPID-2628
> URL: https://issues.apache.org/jira/browse/QPID-2628
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Client
> Environment: Fresh build from current trunk
> Reporter: Chuck Rolke
> Attachments: cpp_bindings_qpid_dotnet_update.patch
>
>
> This issue builds upon or obsoletes QPID-2589.
> The dotnet binding as-is provides only access to the functions in the native
> C++ Messaging API. Customers will need some features beyond that straight
> away. The proposal here is to add a managed dll that wraps the native
> session.nextReceiver() function to provide callbacks through an interface to
> deliver messages to the client.
--
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:[email protected]
