f6c852bf8e
Previously we were publishing one messagebus message per user which was 'tracking' a topic. On large sites, this can easily be 1000+ messages. The important information in the message is common between all users, so we can manage with a single message on a shared channel, which will be much more efficient. For user-specific values (notification_level and last_read_post_number), the JS app can infer values which are 'good enough'. Correct values will be loaded as soon as a topic-list containing the topic is visited. |
||
|---|---|---|
| .. | ||
| badge-test.js | ||
| category-test.js | ||
| composer-test.js | ||
| email-log-test.js | ||
| group-test.js | ||
| invite-test.js | ||
| nav-item-test.js | ||
| pending-post-test.js | ||
| post-stream-test.js | ||
| post-test.js | ||
| private-message-topic-tracking-state-test.js | ||
| report-test.js | ||
| rest-model-test.js | ||
| result-set-test.js | ||
| session-test.js | ||
| site-test.js | ||
| staff-action-log-test.js | ||
| theme-test.js | ||
| topic-details-test.js | ||
| topic-test.js | ||
| topic-tracking-state-test.js | ||
| user-action-test.js | ||
| user-badge-test.js | ||
| user-drafts-test.js | ||
| user-stream-test.js | ||
| user-test.js | ||