On 01/17/2011 02:57 PM, Carl Trieloff wrote:
On 01/17/2011 08:14 AM, Gordon Sim wrote:
Recognise a timeout value that can be passed in the arguments to
queue-declare. Instead of immediately deleting the queue when eligible
for doing so, set up a timed task to try to delete after the
configured delay. If the queue becomes used within that period again,
the delayed deletion will be cancelled.
Why not use session timeout and tie it to that. why introduce another
variable, if the goal is to allow reconnection, we don't need to config
queues
differently on a specific session differently.
Additionally using the session timeout, it becomes more logical. I
failover and I
have till connection session timeout to re-connect.
We don't support session resume so session timeout at the AMQP 0-10
level is not used at present. I prefer to keep this entirely separate
rather than mix it in with that. It is certainly possible to have a
session level timeout value in clients and use that for all temporary
queues.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
