Should I use JMS or any alternative?

Question

Hi,
I need to implement multi-client server system and I have a problem in its architecture. Any help would be great!
The system works as follows. The clients ask for some services, and the server checks the database whether this service is available or not, if yes, it returns some information about the service to the client.
Here it seems, i need to use point-to-point jms. But in this scenario there must n queue for n clients and how can the clients know the name of queues and when (n+1). th client comes then a new queue should be created, but how can the server know about the existence of new client?
Any solution or you think I should chnage to RMI,CORBA?
regards

Answer 1

I don't see why the server should have to maintain more than one queue. The clients can all send messages to the one request queue, and the server can use Message:getJMSReplyTo() to figure out where to send the reply. Each new client will, of course, need to create a new response queue, but the server will always get the queue reference from the request message:
Destination replyTo = message.getJMSReplyTo();
if ((replyTo != null) && (replyTo instanceof Queue)) {
qSender.send((Queue) replyTo, message);
( The client may need to call the setJMSReplyTo method on the message before sending it. )
Depending on the scalability requirements of your application and the intricacy of the messages you're sending you could certainly use RMI instead, but it doesn't sound like you have to use RMI.