[
https://issues.apache.org/jira/browse/QPID-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866530#action_12866530
]
Cliff Jansen commented on QPID-2589:
------------------------------------
> Would it be possible to build the WCF (channel and service
> interfaces) on top of this API?
Well, no. But that is the same answer for the old 0-10 client code and,
nevertheless, the WCF channel uses that for 95% of its work and sneaks around
it for some additional functionality.
In the end, this new API is *much* less rich, which means the WCF channel may
have to work much harder behind the scenes to get its work done. But that
still may be the right balance. The API should be true to the target developer
base first - how many need to be transaction resource managers or perftest
stars?
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).
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. Their absence in this API is not fatal
("just" run another thread to block on a session.sync(true)), but reduces
options for performance optimizations. The current WCF implementation is
impressively speedy and it would be sad to handicap it.
I would be most happy to see things evolve so that the messaging API becomes a
libc-ish entity that can work in an application that simultaneously uses
kernel-ish functionality for finer grained capabilities (without pulling the
rug out from under libc). I am all for keeping the "Advanced" in AMQP.
> 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
