You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Tomas Restrepo (JIRA)" <qp...@incubator.apache.org> on 2007/05/28 01:31:16 UTC
[jira] Updated: (QPID-500) Fix public API to match standard .NET
Conventions
[ https://issues.apache.org/jira/browse/QPID-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomas Restrepo updated QPID-500:
--------------------------------
Attachment: QPID-500.diff
Proposed patch attached. Besides doing the originally proposed, the patch also improves the following:
- Completes the IConnection interface so that it represents all externally-usable methods and properties in AMQConnection.
- Makes a lot of methods and properties in AMQConnection internal so that they can not be modified by outside classes
- Adds Create() method to IConnectionInfo and QpidConnectionInfo, which provides a more convenient way to create connections without hardcoding to AMQConnection:
IConnectionInfo info = QpidConnectionInfo.FromUrl(...);
IConnection connection = info.Create();
- Adds XML documentation to several classes and interfaces in Qpid.Messaging
- Cleans up a bit AMQConnection.cs to extract nested helper classes and make it more maintainable.
> Fix public API to match standard .NET Conventions
> -------------------------------------------------
>
> Key: QPID-500
> URL: https://issues.apache.org/jira/browse/QPID-500
> Project: Qpid
> Issue Type: Improvement
> Components: Dot Net Client
> Affects Versions: M2
> Reporter: Tomas Restrepo
> Attachments: QPID-500.diff
>
>
> Currently the public API of the .NET client is mixture of the original Java Client JMS-Based API and some .NET specific functionality. This makes the API be very inconvenient to use for a .NET developer and feel very unnatural (while still not being faithful to the original Java API).
> Proposed changes:
> - Make public delegates used in message consumers and connection exceptions into proper events that use signatures matcing the .NET guidelines.
> - Make naming of public classes consistent (i.e. AmqChannel -> AMQChannel)
> - Ensure that the IConnection interface contains all useful methods and properties in AMQConnection to make it easier to code to the interface and not the implementation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.