Hey guys I'm making a Wicket 6 application that will use Atmosphere for server push events. I am also planning to use events to communicate between wicket components (for any messages between components not defined in the same class) and possibly to use events/observers for internal application business logic.
One of the guides/examples on using Atmosphere talket about using Guava for application events and just using Atmosphere for server push events to the client. I can understand if you want to keep a loose coupling between a wicket front end and your business logic, but it seems to me that Atmosphere could be used for events, even in the case that you wanted to use another front-end framework. Are there any good arguments for not just using Atmosphere events throughout the application, completely avoiding Wicket and Guava events? Are there significants advantages (for instance performance related) to using wicket native events for the component-component messaging? Is there a consensus about what is best-practice, or is it mainly a matter of taste. Looking forward to hearing your thoughts on the matter. Thanks in advance Jarnis -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Events-Atmosphere-vs-Guava-vs-Wicket-native-tp4657595.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
