[
https://issues.apache.org/jira/browse/QPID-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866533#action_12866533
]
Gordon Sim commented on QPID-2589:
----------------------------------
> The major outages are dtx support and message body content optimizations (one
> time set, one time retrieve, i.e. the WCF paradigm, and I would argue a not
> uncommon scenario).
These are certainly gaps we would want to address in the messaging API and its
implementation.
> Off the top of my head, I also worry about the limited async functionality.
> The current WCF implementation relies heavily on async related classes in the
> old API, such as Future and Completion.
I'd be keen to explore these worries in some more detail. Could we tackle one
or two concrete cases to begin with?
> 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:dev-subscr...@qpid.apache.org
