We apologize for the instability of composr.app and appreciate your patience. We are working on the statistics addon and trying to find an optimal way to store and render data. Unfortunately, we have yet to find a solution that can handle the traffic (and therefore, tens of millions of statistical records) of composr.app. We're working hard on one.
I suspect this is more complex than you think to do well enough for mainstream Composr...
1) We would need to have a "has not changed" signal that is extremely efficient, preferably before any database connection is opened. This is how the AJAX checks for notifications and chat messages work, because people will leave things open a long time so the regular checks have to be very fast to process.
2) If pagination is active and you're not on the last page, it shouldn't show new posts (presumably).
3) If threaded view is active we definitely shouldn't refresh the whole topic, so we need to load up individual posts properly, and insert them in the right positions in the tree.
Previously I was also concerned about adding table rows dynamically without making deep assumptions about templates, but with modern browsers this should not be an issue, and we moved to divs anyway.
1) We would need to have a "has not changed" signal that is extremely efficient, preferably before any database connection is opened. This is how the AJAX checks for notifications and chat messages work, because people will leave things open a long time so the regular checks have to be very fast to process.
2) If pagination is active and you're not on the last page, it shouldn't show new posts (presumably).
3) If threaded view is active we definitely shouldn't refresh the whole topic, so we need to load up individual posts properly, and insert them in the right positions in the tree.
Previously I was also concerned about adding table rows dynamically without making deep assumptions about templates, but with modern browsers this should not be an issue, and we moved to divs anyway.