Re: Events: Atmosphere vs. Guava vs Wicket native
Hi Jarnis. Since this didn't generate a response, I'll share some thoughts. First a disclaimer: I haven't used Wicket-Atmosphere yet, but I've read what there is to read and am looking forward to it. (We have several use cases that will benefit greatly.) Are there any good arguments for not just using Atmosphere events throughout > the application, completely avoiding Wicket and Guava events? Are these events changing the DOM in ways Wicket should know about? It seems like most non-trivial event content would require corresponding changes to your Wicket component graph, e.g. preparing for clicks. But if you have a container that doesn't need to interact with Wicket, and you don't mind writing the client- and server-side plumbing directly, maybe it makes sense. > Are there significants advantages (for instance performance related) to > using wicket > native events for the component-component messaging? Wicket's built-in events work well within the Wicket architecture. If a random event comes in on a Guava bus, you have to ask yourself, "okay now how do I get access to this or that component that's serialized in the page store?" Wicket events have well-defined access to the important objects (Application, Session, RequestCycle, Page, Components), and a simple way to target only a subset of those. I don't think server-side performance should be your concern here. Unless you have a super crazy component count Wicket events are plenty fast. Hope that helps. Dan
Events: Atmosphere vs. Guava vs Wicket native
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: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
