You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: