what technology & architecture to choose for a display board

manpreet Best Answer 3 years ago

His to everyone,

I have actually 2 questions in one :) I am about to start into a new project, which is basically a display board (similar to what you see in airports or stock exchanges but for another purpose). It should have many text items, price tags, and buttons for selection. The whole thing should run in a browser and reflect real-time changes (such as frequent updates of prices, and rearrangement of items).

Technology

First choice of technology that comes to mind is GWT that helps to keep traffic low and allows for targeted updates of display areas (since rendering happens on the client side). Based on my experience, there are some cons with this choice however: porting HTML and CSS from static layouts is much more time-consuming in GWT since you only see generated HTML at runtime (UiBinder makes is somewhat more convenient, but the problem at large remains), DevMode is excruciatingly slow under Linux and compiling a permutations for a single deploy can take minutes. Which all contributes to much slower development times than with say JSP or JSF.

Is there some other technology or approach that is very low-key in terms of traffic and is able to display data changing in a real time? We obviously don't want to save the whole new page if some price tag changes its value or position on the display. And faster development times would be a treat :)

Architecture

What would be an appropriate pattern to adopt for this case. I've tried having an index object that would contain references to other price and item objects. So that if arrangement of price tags changes on the screen, new ones arrive, old ones get updated a new index object is created and sent to the client. The client knows than that the display should be updated and renders it anew. The positive thing is that it gives you many reusable components (price and item object), on the negative side though is that this rerendering of the whole screen, if a new item is added, is becomes CPU intensive as more updates come. There is also no one-to-one correspondence between index object and layout of the page: so if you designer has chosen a table-based layout and there is one empty row between item 1 and item 2 then you cannot map index position of the item object to its position on the owning table without some additional processing.

I will be watching shortly the event bus pattern presented in one of the Google videos on GWT. Have a feeling that this might also give a guidance on the right path.

Many thanks for your suggestions!

Update: wording & style