Hey All Does anyone see some flaws with the following kind of framework? The idea is to remove the need for a command pattern for UI-server communication and have just events flying around. I believe I posted a similar thread ages ago, but this is subtly different.
1. UI fires event to event bus. 2. Some events are registered as server events (maybe through the extension of a ServerEvent, or ServerClientEvent for both) 3. The event gets sent to 1 service on the UI side 4. The service has got event handlers registered and distributes the events to the correct handlers (perhaps using threads for concurrency so that all your server operations can happen simultaneously) 5. It then waits on all threads to terminate (of course there could be only one!) 6. It groups all the responses together 7. Sends responses back to the client 8. UI fires off a response received event specific to each of the responses received 9. UI registers those responses and processes them -- 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.
