> What is the best way to implement publishing in a multi-threaded app ?
> Is
> it best to have a single publisher, protected by synchronization, or a
> pool
> of publishers arbitrated by a manager. If the latter, what factors
> should
> be used to determine the optimum number of publishers (i.e. memory
> constraints, number of concurrent requests, etc).
It is not a very much difference, because synchronization takes place at
the connection/session. Multiple publishers make only sense when having
multiple connections and maybe a multiprocessor server for the router to
handle request true concurrently. There is a little overhead when using
unidentified publishers, because the topic etc must determined on each
publish call.
--
Andreas Mueller, [EMAIL PROTECTED], IIT GmbH, Bremen/Germany, http://www.iit.de
SwiftMQ, JMS Enterprise Messaging System, http://www.swiftmq.com
-----------------------------------------------------------------------
Support SwiftMQ! PLEASE vote for SwiftMQ as "Best Java Messaging Tool":
http://www.sys-con.com/java/readerschoice2001/
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
