Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Won't Fix
-
None
-
None
Description
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.