Why use a message selector instead of simply filtering messages at the consuming client level by, for example, scanning the message body based on certain criteria?
Location: http://www.jguru.com/faq/view.jsp?EID=1160 Created: Nov 19, 1999 Author: Jerry Smith (http://www.jguru.com/guru/viewbio.jsp?EID=9) There are at least three reasons. First, in most cases, client-side filtering is quite a burden to implement, for example, parsing a textual message. Second, if the message type were, say, Object, it could be burdensome for the producer to “decorate it” with selection criteria and/or for the consumer to select messages based on those criteria. Third, using a selector is more efficient because the JMS server avoids having to send the filtered message to the consumer.
Related Questions
- While trying to receive messages in my email client, I get a message saying, "The host pop.net4india.com could not be found. Please verify that you have entered the server name correctly", why?
- Why use a message selector instead of simply filtering messages at the consuming client level by, for example, scanning the message body based on certain criteria?
- Does the EPCS spam filtering process look at the content of e-mail messages to determine if it is a spam message?
