[
https://issues.apache.org/jira/browse/QPID-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510361
]
Alan Conway commented on QPID-536:
----------------------------------
We need a generic solution to this that can be used in the Proxy objects also
so that the client internals can be refactored to use the proxy rather than the
current ResponseHandler approach. I think we need to implement a generic Future
pattern, e.g. see
http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/Future.html
This provides a general solution for client-side to use or ignore async results
as it sees fit, and for exceptions to be transferred to client threads
(internally the future would hold a clone() of the original exception and throw
it from get() )
> allow application to register for exceptions resulting from non-blocking calls
> ------------------------------------------------------------------------------
>
> Key: QPID-536
> URL: https://issues.apache.org/jira/browse/QPID-536
> Project: Qpid
> Issue Type: New Feature
> Components: C++ Client
> Reporter: Gordon Sim
> Assignee: Gordon Sim
>
> E.g. publish is not synchronous but the application may like to register a
> listener to be notified if it fails.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
