I'm playing around with LVQs, in particular in conjunction w/ttl semantics for expiration of keys/symbols.
I noticed that if I post a message for a given LVQ key, it's not possible to change its TTL of a key "on the fly". The TTL of the initial message seems to be the one in effect - even though browsing the messages will show the latest (incorrect) TTL value. To reproduce: * Send a message w/ ttl=5 LVQ_key=bar * Send another message w/ ttl=3600, LVQ_key=bar The message will expire and get purged after 5s. Is this expected behavior? It seems it would be pretty useful and consistent that the properties of the last posted message are effective? /Daniel PS. Tested on both 0.6 and trunk. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
