This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
I already googled the topic and fliped over the JMS specs, but I didn't find any hint nor an answer yet so I really hope you can help:
I need to implement a software where people can monitor the status of an object in realtime and thus get informed about status updates immediately. It's not really highly critical, but queuing a message and let the consumers fetch it is not an option. It has to be a 'push' mechanism that sends the message to the consumer right away.
Would a JMS publish-subscribe solution fit that needs?
Thanks for the quick reply, but the question was not about the design of the application but rather if J2EE servers are required to be implemented that way, that the connection to consumers is kept alive and messages are pushed to them.