[
https://issues.apache.org/jira/browse/QPID-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868317#action_12868317
]
Gordon Sim commented on QPID-2589:
----------------------------------
Re implementing "WCF's BeginSend for asynchronous writes", one suggestion for
that is to maintain a counter for each sender tracking the messages sent. The
AsyncResult for a BeginSend would then include the value of the counter for
that send, lets call it x. If for any given send, counter -
sender.getUnsettled() > x, that send has completed. Does that sound workable?
You would still want a way to wait for changes to the unsettled list. The
desire to improve the general threading by adding some generic mechanisms like
this has been discussed and should be a future focus for the messaging API.
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.
Note also that with the messaging API the replaying of messages would be part
of the underlying functionality.
> 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
