While polling, etc. are nice concepts that are quite easy to grasp and
implement, I'd very much like to see some sophisticated event bus solution
employed in RHQ (spanning the server and clients).
We might not see the possibilities or use cases right now but tying ourselves
to a more "primitive" technology (that, after all, the event buses build upon)
would later require us to invest much more time into refactoring/restructuring
the code.
We already discussed the deficiencies of our GUI, which we ran into by choosing
an obsolete development model (GWT pushes the MVP style of development but we
chose swing-like approach, even though we knew about its scalability
problems). Let's try and pick carefully this time.
On Tuesday, July 31, 2012 15:45:15 John Mazzitelli wrote:
> Nothing really specific ; it could even be a part of the UI that
just
> polls some generic API every second and then informs other parts in the
> UI.
This is how I implemented that fast prototype I did with the UI messages
coming from the agent. Used polling.
> Perhaps GWT or SmartGWT also offers something similar out of the box
There is the concept of a GWT timer. Just something that gets triggered
after N milliseconds. You can implement a simple polling mechanism using
that and have it continually poll the server. This is what Errai helps with
- IIUC, Errai avoids the need to continually poll, since it involves
pushing from server to gwt client. But we don't currently integrate with
Errai as we all know. _______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel