| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Trigger or not to trigger |
« View previous topic :: View next topic » |
| Author |
Message
|
| mike@home |
 Posted: Tue Jun 25, 2002 3:56 am Post subject: Trigger or not to trigger |
 |
|
Newbie
Joined: 25 Jun 2002
Posts: 1
|
Hi I just wanting some design guidelines on when to use or not use triggering (no MQ clients).
For in-bound messages it would seem to me a bit of a overhead to be always opening & closing queues and having the queue always open to be a preferred approach.
For out-bound messages what techniques are available for sending out messages while always being connected to the output queue
Thanks
Mike |
|
| Back to top |
|
 |
| mgrabinski |
| Posted: Mon Jul 01, 2002 9:33 pm Post subject: |
|
|
Master
Joined: 16 Oct 2001
Posts: 246
Location: Katowice, Poland
|
To trigger or not to trigger depends on your application. For example, if messages arrive steadily, it may be better to have the queue open instead of triggering. On the other hand, when messages arrive seldom, triggering would best.
In my practice I've found that usually the most benefitting approach is to combine the two methods. Start with triggering and wait a specific period of time for next messages. If nothing arrives, close down. During tests you can measure the message flow, CPU usage and so forth. This data will enable you to decide the proper design for your case.
Best regards,
_________________
Marcin Grabinski <>< |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
