I am using messaging within Blaze, and my application needs a fallback
solution if the Blaze server is disabled for any reason. My fallback
is to do application polling via HTTPService to get the required data.
I have got that side working.

When I do my testing to simulate the Blaze server being disabled, I
stop the web server, and my application successfully falls back to get
the data on a polling mechanism with a 15 seconds interval from a
database via HTTPService. It works. Just after I do a polling loop I
initiate a subscribe to the consumer service. I have an event listener
on the consumer ChannelEvent.CONNECT that when fired will stop the
application polling.

Trouble is that even though the subscribe is called the connection is
never established.

1. Should I be able to re-connect after the server hosting Blaze stops
and then starts again.

2. What is the best way to simulate a disabling of the Blaze server
for testing puposes.

Andrew

Reply via email to