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. |
||
|---|---|---|
| .. | ||
| component-test.js | ||
| create-pretender.js | ||
| create-store.js | ||
| d-editor-helper.js | ||
| fixture-pretender.js | ||
| presence-pretender.js | ||
| qunit-helpers.js | ||
| review-pretender.js | ||
| select-kit-helper.js | ||
| site-settings.js | ||
| site.js | ||
| store-pretender.js | ||
| textarea-selection-helper.js | ||
| widget-test.js | ||