Is my understanding correct here? A stream queue is another name for the queue the publisher puts to.
The stream queue needs to be separate from any subscriber queues, i.e. you can't have a subscriber specifying the stream queue for subscriptions All publishers could send to the SYSTEM.BROKER.DEFAULT.STREAM. But you probably don't want to do that. Assuming 2 publishers will never publish on the same topic, should I create a stream queue per Publisher? Or per Topic? If I'm building a Topic Connection Factory for a Subscriber in JMSAdmin, what do I put for the Publication Stream parameter? XXXXXX? That parm doesn't apply at all to a subscriber, right? What to do - a Subscriber MQ queue defined per Topic, and multiple subscribers read from it, or a Subscriber queue per Subscriber, and when they register they tell the Broker what topics to send to it? (Geez, it feels like 2001 all over again when I cracked open an MQ manual for the first time and had questions about Expiry :-). This Pub Sub stuff...yikes!) Peter ************************************************************************* This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. ************************************************************************* To unsubscribe, write to [EMAIL PROTECTED] and, in the message body (not the subject), write: SIGNOFF MQSERIES Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
