He Feroz, Just another idea to stop-and-wait which I use:
I use events everywhere across my app to control what should happen, like app-init, start-..., etc.. The events are catched by pieces of code that can indicate in the received event, that it must wait further dispatching any event (= stopping the app). When the response is received, I inform the event that it can continue, such that the central dispatcher will start dispatching all events that it had received after the wait request. I use this mainly during startup to load some CMS files. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
