[
https://issues.apache.org/jira/browse/QPID-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867223#action_12867223
]
Gordon Sim commented on QPID-2589:
----------------------------------
> I see the nextReceiver() call, but as I see it, this requires a dedicated
> thread per Session to poll for the client's next message, whereas the 0-10
> allowed a single thread or small pool to service the handed off message from
> all sessions.
Actually I don't think that is correct, the old 0-10 API also required a thread
per session, at least at the c++ level. However going forward we do want to
change that. One of the problems was the lack of support from the old client
(in those parts on which the new client was built).
I'll work through your examples on async send above, thanks for posting them!
> Add a .NET binding to QPID Messaging API
> ----------------------------------------
>
> Key: QPID-2589
> URL: https://issues.apache.org/jira/browse/QPID-2589
> Project: Qpid
> Issue Type: New Feature
> Components: C++ Client
> Affects Versions: 0.7
> Environment: Windows
> Reporter: Chuck Rolke
> Assignee: Ted Ross
> Fix For: 0.7
>
> Attachments: qpid_bindings.diff
>
>
> This binding package is a .NET Interop wrapper around the Qpid Messaging
> interface. It exposes the Messaging interface through a series of managed
> code classes that may be used by any .NET language.
--
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]
