[
https://issues.apache.org/jira/browse/QPID-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross closed QPID-2978.
-----------------------------
Resolution: Won't Fix
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
