I am investigating using JavaScript in Chrome to display transaction data for a kitchen display system. I am wondering how robust this would be for client side JavaScript fetching data from a server and updating the displayed information for hundreds of transactions, days at a time.
The basic architecture is to have a web page to display transaction items in several columns, one column per transaction. As the order is assembled and then given to the customer, the transaction would be bumped meaning it would be removed from the display. As new transactions are fetched from the server, the displayed list of transactions would be updated with the new transactions. Bumping a transaction will cause transactions displayed to the right to ripple down to fill in the now empty column.
My concern is whether using JavaScript to drive a Client display will have the necessary resource garbage collection so that it will be able to run for days at a time while dynamically updating and changing the displayed information.
There seems to be two tasks: (1) fetching the data from the server and (2) updating the displayed information through document DOM manipulation.
I would assume that different browsers using different JavaScript engines would have different robustness characteristics. Is there any information on the subject of JavaScript engine robustness when used under similar conditions?