How do meteor subscriptions work?

Question

JavaScript

Good evening! I need some info about meteor subscriptions. Namely, when working with iron:router.
In each route, I have waitOn set, which ensures that the data is loaded in a timely manner.
When publishing, I use the publish-composite package, which provides some sugar. So, when moving from one route to another, if the same collections are used, is everything reloaded or just updated to the current state?

Answer 1

Here is a great article about optimizing subscriptions, you will find the answer there
ps: I advise you to move to flow-router :)

Answer 2

If on route A you have Meteor.subscribe('getAllPost'), and on route B you have Meteor.subscribe('getSinglePost'), then the getAllPost subscription will be terminated and the data from the client will go to oblivion. In general, as I understand it, you are talking about caching, as far as I know, there is no caching of subscriptions out of the box in the meteor. waitOn provides you with a timely loading of data from the server and shows the loader, for example.
PS: Don't forget that publish-composite publishes both parent and child fields, and most likely even all fields.