[ https://issues.apache.org/jira/browse/QPID-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner resolved QPID-500. -------------------------------- Resolution: Fixed This is as done as it's gonna get. Nobody should use the 0-8 impl for new work really... > 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, M2.1, M3, M4, 0.5, 0.6 > Reporter: Tomas Restrepo > Assignee: Aidan Skinner > Fix For: 0.6 > > 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. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org