posted 20 years ago
Hmmm, I thought synchronous MQ was as simple as using the getAndWait() API to wait for the message to come back and pull it off the queue. We use this on an app server where the client thinks it is calling a synchronous service. We have to wait for the MQ response before we return to the client. I've always had a wrapper around MQ, not really written to the MQ API mice elf.
We use MQ as synchronous and asynchronous RPC, which is not usually a problem that suggests MQ as an answer. But after some effort we got outstanding performance and reliability out of MQ.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi