Using meteor method with reactivevars on termplate to grab and reactively update data


I was having trouble implementing well functioning pagination / infinite scroll with the regular pub / sub techniques. I switched to a meteor method and reactive vars on the client to fetch only the data currently needed and storing them on a reactivevar in the template. This seems to function better and make more sense then the pub / sub method i was trying.

Wanted to see if there’s any downsides to this method that I’m not thinking of and if not why don’t I see other people using this method?


If i understand well what you have done, changes on the data made by an other client during the session won’t be propagated to data in your reactive var. You are losing much of the benefit of the Meteor architecture.


This was for a userlist / filtering so it doesn’t really need any live data updates