You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2015/03/16 21:19:42 UTC

[jira] [Resolved] (QPIDJMS-26) move to using the Events API now available Proton

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

Robbie Gemmell resolved QPIDJMS-26.
-----------------------------------
    Resolution: Fixed

> move to using the Events API now available Proton
> -------------------------------------------------
>
>                 Key: QPIDJMS-26
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-26
>             Project: Qpid JMS
>          Issue Type: Improvement
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>
> More recent versions of Proton have added an Events API, which can allow for simpler and more efficient usage for tasks such as determining changes which have occurred due to processing transport input and additionally signalling pending output. We should move to using the Events API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org