Separate inquiry and reply queues in the CAM

 

The application could use a single queue for both inquiries and replies, but it was designed to use separate queues for the following reasons:

• When the program is handling the maximum number of inquiries, further inquiries can be left on the queue. If a single queue were being used, these would have to be taken off the queue and stored elsewhere.

• Other instances of the CAM could be started automatically to service the same inquiry queue if message traffic was high enough to warrant it. But the program must track in-progress inquiries, and to do this it must get back all replies to inquiries it has initiated. If only one queue were used, the program would have to browse the messages to see if they were for this program or for another. This would make the operation much less efficient.

  The application can support multiple CAMs and can recover in-progress inquiries effectively by using paired reply-to and waiting queues.

• The program can wait on multiple queues effectively by using signaling.

 

Parent topic:

Design considerations

fg18640_