Subscrbe is too slow

[streemo]

@delfa

So for the same query as above (“get the last 10 posts”), I need to write publishs, subscribtions and add the logic twice (on server and client) which is very unattractive (what if I change something?).

I was flirting with a possible solution to this a few months ago…

This would make it so you only have to write the query logic on the server, vastly simplifying your client side:

Caching subscription ids in minimongo to vastly simplify client-side querying

Imagine that we have 10 pubs for posts. That’s a lot branching and code on the client. Here is a hack I can do to make every query on the client the same (lets just assume cached subs). Meteor.publish('posts-seven', function(params){ //check params, set self, get someQuery here; var helper = Posts.find(someQuery).observeChanges({ added:function(id,fields){ fields[getSubId(self)] = true; self.added('posts',id,fields); } //... include canonical changed/removed here }…

In summary:

In your publication (on server) you would use the added/changed/removed API to tack on the subscription id to each document before sending it down to the client via something like {“SuBScRiPtIoNiD”: true}.

On the client, you would merely have to query MyCollection.find({‘SuBScRiPtIoNiD’:true}). You could easily make all of your subscriptions template-level, and keep track of each active subscription in the template state, via a template reactive instance variable, for example.

Hope this helps you a little bit at least.