Skip to content
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.

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

Caching issues, and waiting for "real" (i.e. not fast-rendered) data #175

Open
SachaG opened this issue Jul 1, 2016 · 0 comments
Open

Comments

@SachaG
Copy link

SachaG commented Jul 1, 2016

The way fast-render works is that it "tricks" Mini-mongo into thinking data is loaded right from the start, before Meteor ever subscribes and gets its data via the normal DDP channel.

But I'm running into an annoying issue: I want to cache my pages via Nginx, meaning the fast-render part of the initial payload will also be cached.

This means there might be discrepancies between the fast-render data and the "real" DDP data. That's not a huge problem since any discrepancy will self-correct reactively once the DDP data kicks in, but it does lead to a few issues in my app.

So I would love to know if there's any way to test for when a subscription is "really" ready, in the sense that it's receiving its data via DDP and not from fast-render?

Alternatively, any recommendation for handling caching and fast-render together?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant