2008/5/21 Robert Greig <[EMAIL PROTECTED]>: > 2008/5/20 Senaka Fernando <[EMAIL PROTECTED]>: > >> <heartbeat> >> <delay>0</delay> >> <timeoutFactor>2.0</timeoutFactor> >> </heartbeat> > > This controls the heartbeat settings, that are used to detect client > failures. A non-zero value specifies the time between heartbeats (I'm > guessing the units are seconds but you may want to check that). The > timeout factor specifies the multiple of the delay that is allow to > pass without receiving a heartbeat before the client is considered > dead. For example, if the heartbeat delay was 10 seconds and the > factor 2.0, then after 20 seconds the client would be considered dead. > >> <queue> >> <auto_register>true</auto_register> >> </queue> > > This is an interesting one. If specifies whether queues get > automatically bound to the direct exchange when declared. Rob - is > this actually specified in the 0-9 protocol now? If it is then > obviously it should be removed as an option.
0-8/0-9 Specify that every queue that is created should be automatically bound to the "no-name" exchange; which is a direct exchange. This behaviour is still mandated in 0-10. This config file option (when set to true) provides this AMQP compliant behaviour :-) > The reason this is an option was to make it compatible with openamq. I > strongly objected to that behaviour at the time, since it was only > introduced because that product had an API that mirrored the protocol. > I believed at the time, and still do for that matter, that it was done > for the wrong reasons - because someone viewed the protocol as an API > and wanted to provide some syntactic sugar. I *think* that the intention is to allow for a simplified model for those that do not wish to understand the concept of exchanges. -- Rob
