[
https://issues.apache.org/jira/browse/QPID-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867271#action_12867271
]
Ted Ross commented on QPID-2589:
--------------------------------
Expanding on my last comment...
The .net code in this binding should never add any "messaging" value to the
API. If we want to add new features, they should first be added to the C++
messaging API and then reflected through this binding.
Also, with regard to the location of this code... The "bindings" directory
under qpid/cpp is intended to hold other-language bindings to C++ interfaces.
We might want to eventually supply messaging bindings for Python, Ruby, Perl,
PHP, etc. so that these interfaces can be more easily supported and can benefit
from the features and performance of the C++ API.
-Ted
> 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, 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
