f14189eb3b
When a client "reads" a post, we do no immediately send the data of the post for processing on the server. Instead, read posts data is batched together and sent to the server for processing at regular intervals. On the server side, processing of read posts data is done in the background. As such, there is a small window of delay before a post is marked as read by a user on the server side. If a client reads a topic and loads the messages topic list before the server has processed the read post, the unread posts count for the topic which the client just read will appear to be incorrect/outdated. As part of tracking a post as read, we are already tracking the highest read post number for the last read topic by the client. Therefore, we can use this information to correct the highest post read number in the scenario that was described above. This solution is the same as what we've been doing for the regular topics list. |
||
|---|---|---|
| .. | ||
| app | ||
| config | ||
| lib | ||
| public/assets/scripts | ||
| scripts | ||
| tests | ||
| .ember-cli | ||
| .npmrc | ||
| ember-cli-build.js | ||
| jsconfig.json | ||
| package.json | ||
| testem.js | ||