qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Ross (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-2978) Disconnected operation is a pain
Date Fri, 15 Feb 2013 13:11:13 GMT

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

Justin Ross updated QPID-2978:

    Priority: Minor  (was: Major)
> Disconnected operation is a pain
> --------------------------------
>                 Key: QPID-2978
>                 URL: https://issues.apache.org/jira/browse/QPID-2978
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Client, Python Client
>            Reporter: Justin Ross
>            Priority: Minor
>             Fix For: Future
> If you're writing a program that doesn't expect a tcp connection to be present all the
time, the messaging API currently gives you some unattractive options.
> If you set conn.reconnect = True, conn.open() will block, and you'll never get to all
the other code you'd prefer to have executed.
> If you leave conn.reconnect = False, conn.open(), session.sender(), and conn.close()
will throw exceptions that have to be caught and ignored.
> In either case, session.send() will throw an exception.
> I'd like some way to tell the connection that I'm really quite indifferent to whether
or not the underlying tcp connection is active.
> I did this testing using the python api, but word has it that this may be the case for
the C++ api as well.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

View raw message