You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "james strachan (JIRA)" <ji...@apache.org> on 2007/02/27 11:39:06 UTC

[jira] Moved: (AMQNET-33) IConnection requires Start(), Stop() and Close() methods

     [ https://issues.apache.org/activemq/browse/AMQNET-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

james strachan moved AMQ-996 to AMQNET-33:
------------------------------------------

        Fix Version/s:     (was: 4.1.0)
                       1.0
          Component/s:     (was: NMS (C# client))
    Affects Version/s:     (was: 4.0.2)
                  Key: AMQNET-33  (was: AMQ-996)
              Project: ActiveMQ .Net  (was: ActiveMQ)

> IConnection requires Start(), Stop() and Close() methods
> --------------------------------------------------------
>
>                 Key: AMQNET-33
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-33
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>         Environment: Windows
>            Reporter: Rob Lugt
>         Assigned To: james strachan
>             Fix For: 1.0
>
>
> These three methods are needed to bring IConnection closer to the JMS Connection interface, and also provide important capabilities.
> Start() and Stop() methods should start and stop/join the underlying transport's reader thread.  Close() should perform the tasks described in the JMS specification (ie wait for current message to be processed), whereas Dispose should probably concern itself simply with freeing up resources.
> Both Close() and Dispose() should be able to be called multiple times without throwing an exception.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.