Skip to content

typo line 88, page -> pages #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
airyclam wants to merge 1 commit into
base: master
Choose a base branch
from
Open

typo line 88, page -> pages #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/developers/design/app/imports/api/pub-sub.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ The point of this section is to note that the default approach to pub-sub in Met

The advantage of the default approach is simplicity and minimization of the data held by the client at any given time. The disadvantage is that if two pages involve the exact same set of subscriptions, and the client navigates from one of these pages to the other, then the default approach results in data being sent to the client for first page, then discarded when the client leaves that page, only to have the server resend the exact same data to the client when the second page is loaded.

Upon deploying RadGrad for the first time, we discovered that page were loading slowly and that much of this latency was due to the overhead of subscribing and unsubscribing each time the client visited a new page. To solve this problem, RadGrad leverages the [MeteorHacks SubsManager](https://github.com/kadirahq/subs-manager) package, which provides the ability to cache subscription data on the client side.
Upon deploying RadGrad for the first time, we discovered that pages were loading slowly and that much of this latency was due to the overhead of subscribing and unsubscribing each time the client visited a new page. To solve this problem, RadGrad leverages the [MeteorHacks SubsManager](https://github.com/kadirahq/subs-manager) package, which provides the ability to cache subscription data on the client side.

Our implementation of subscription caching is accomplished by three global templates:

Expand Down