On 7/19/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Totally unrelated ... JMS has the ability to create a message filter, but one of the limitations is that the filter is applied when the receiver is created, rather than when a get operation is executed. This makes sense for the push receiver case, but is limiting for the pull receiver case. Does AMQP have anything to say about this aspect of messaging, or does it stay strictly in the messaging provider space, and away from the client API?
Could you explain a little more about your use case - it sounds interesting :). Do you only want to fetch a single message with a different filter per message, or just change the fliter from time to time. If its the latter then creating JMS consumers is pretty cheap & you can use any JMS to do that. Though the former, there's no 'give me a message using filter X' type operation. FWIW it wouldn't be too hard to add this to blaze or activemq - its just a different kind of operation. Messaging systems are usually designed for asynchronous streaming of messages, so you subscribe and receive many messages etc. -- James ------- http://radio.weblogs.com/0112098/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
