You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are web sockets still the blessed way of pushing data to sync up state in multiple remote clients? Where do service workers come in?
Right now we're hackily pulling data back via window.setInterval and it's all a bit awful. Before we go too much further down that path let's investigate the blessed way to push data to clients.
We'll need to make it work for:
Triagers
A reviewer coming online / going offline
A reviewer changing the status of a work assignment
Are web sockets still the blessed way of pushing data to sync up state in multiple remote clients? Where do service workers come in?
Right now we're hackily pulling data back via
window.setInterval
and it's all a bit awful. Before we go too much further down that path let's investigate the blessed way to push data to clients.We'll need to make it work for:
Triagers
@todo
Handle intelligently discarding received tweet objects if we have enough to show a column (i.e. 20/column)loadMoreRows
(these always need to be stored)Handle intelligently discarding tweet objects that are "too far away" from the current view of all columns it appears inHandle user-toggleable filters for "Show me completed tweets" and "Show me discarded tweets" and how that impacts column totalsHow do we handle new tweets that arrive while the user is disconnected?Handle maintaining position and scrolling to tweets. Ideally, saving it between page loads.Refer to and cleanup Optimisations #18Fix the issue with tweet mediaReviewers
Application
Resources
The text was updated successfully, but these errors were encountered: