I'm evaluating Real-Time Messaging in an application in which the user initiates some request - runFooCheck() - which is an RPC call that does some processing on the server which could take some indefinite amount of time, at the end of which a message is pushed to the client using the ISCMessageDispatcher.
I'm currently configured to use "Enterprise messaging" mode, using ActiveMQ and Tomcat following the instructions here: https://isomorphic.atlassian.net/wik...t+and+ActiveMQ
I want to know if it's possible for a client to receive the server-pushed message without being currently subscribed at the time the message was pushed. That is, a user clicks a button which initiates the runFooCheck(), closes their browser window for some inordinate period of time, meanwhile runFooCheck() completes and the ISCMessageDispatcher has pushed the resulting message onto the channel/Topic. When the user re-opens their browser window, they are re-subscribed to the channel, and they immediately receive the message that was there waiting for them.
Is this possible to achieve with Real-Time Messaging? Or is this a pipe dream?
I'm currently configured to use "Enterprise messaging" mode, using ActiveMQ and Tomcat following the instructions here: https://isomorphic.atlassian.net/wik...t+and+ActiveMQ
I want to know if it's possible for a client to receive the server-pushed message without being currently subscribed at the time the message was pushed. That is, a user clicks a button which initiates the runFooCheck(), closes their browser window for some inordinate period of time, meanwhile runFooCheck() completes and the ISCMessageDispatcher has pushed the resulting message onto the channel/Topic. When the user re-opens their browser window, they are re-subscribed to the channel, and they immediately receive the message that was there waiting for them.
Is this possible to achieve with Real-Time Messaging? Or is this a pipe dream?