CODEWITHSUNDEEP
javascriptmeteor
zigo
zigo

Reputation: 159

Meteor reactive publish based on client session variable

I'm making a meteor js web app that presents the client an html range slider tied to a session variable.

I want the server to only publish data with values less than the current value of the slider with data sorted from newest to oldest. I have a lot of database entries (2000+). If I publish everything within the max of slider my browsers too slow. If I limit the publish to 100 entries or so, I miss out on a lot of data with small values (which happen to be older) when I bring the slider down.

What are the best practices for trying to be scalable (not sending too much data to the client)? Is a reactive publish function the key (using onchange with the slider value as the key)? That sounds like a lot of server round trips. Help!

Upvotes: 0

Views: 792

Answers (1)

Dan Dascalescu
Dan Dascalescu

Reputation: 151893

Would pagination be acceptable from a UX standpoint? If so, there are packages that may help, for instance alethes:pages.

Otherwise, Adam is on the right track by suggesting to use Tracker.autorun (Tracker has replaced Deps).

As with any other publication, make sure your publish function only returns the fields that you need on the client, in order to minimize the data transferred and the memory consumption.

Upvotes: 1

Related Questions