Seems reasonable to me. I don't know offhand if the python will work
with floats currently, but it should be trivial to make that work if it
doesn't already.
--Rafael
On 02/01/2012 10:21 AM, Alan Conway wrote:
Presently the C++ client takes options for reconnecting
(reconnect-timeout, reconnect-interval-min/max etc.) in seconds. A
second is too long for applications that require rapid fail-over. I'd
like to make these values more fine grained, but I don't want to break
the existing interface.
Proposal: Have C++ treat reconnect time values as floats, so e.g.
reconnect-interval-min=0.001 sets a millisecond as the minimum
interval. Existing code will be unaffected. I believe this is already
the case for the python client, since python normally expresses time
in floating-point seconds.
Does anyone see a problem with this approach or have an alternative
suggestion? The only alternatives I can think of are:
- break backward compatibility and re-interpret reconnect values as
milliseconds or nanoseconds rather than seconds.
- add another set of reconnect-timeout-ms or reconnect-timeout-ns
options on top of the existing second options.
I don't like either of those.
Cheers,
Alan.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
