[ 
https://issues.apache.org/jira/browse/QPID-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868362#action_12868362
 ] 

Cliff Jansen commented on QPID-2589:
------------------------------------

Thank-you Gordon for turning your mind to this.

> You would still want a way to wait for changes to the unsettled list. 

Much better would be an event notification, see below.  But otherwise, that 
plus "sender.getUnsettled() > x" should do the trick.

> However I don't think the messaging API is any worse in this respect
> than the old 0-10 API which required either busy-polling or syncing.

Well, the WCF channel uses Future.wait() which is better than either of those 
options.  Even that strategy was criticized during WCF design meetings at 
Microsoft as "wasting" a thread resource for each session that witnessed async 
writes (imagining an application that might simultaneously be servicing 100's 
or thousands of sessions).

A better pattern for high performance WCF would be to be able to register for 
notification of various events, such as message arrival, command completion 
(for message send and dtxFoo) that arrive in the context of the Windows IO 
completion port thread that the socket implementation manages.  This may matter 
much less on Linux, but I expect there would still be a class of developers who 
would appreciate some form of event notification.


> 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: cpp_binding_dotnet.patch, map_receiver_update.patch, 
> 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:dev-subscr...@qpid.apache.org

Reply via email to