Optimization: customize the publish/subscribe methods about meteor-streams HOT 5 OPEN

How does this relates to meteor-streams?

This might help you anyway.

from meteor-streams.

(sry - I accidentally submitted the question too early - just edited)

from meteor-streams.

Hope this would work.

Notifications = Meteor.Streams('notifications');

if(Meteor.isClient) {
  Notifications.emit('active', true);
}

if(Meteor.isServer) {
  var states = {};
  Notifications.on('active', function(state) {
    states[this.subscriptionId] = state;
    this.onDisconnect = function() {
      delete states[this.subscriptionId]
    };
  });

  Notifications.permissions.read(function() {
    return !!states[this.subscriptionId];
  }, false);
}

Anyway, we need a better and simple easy way to do this. I will add a new API. But not sure about the timeline.

from meteor-streams.

SWEET! thanks for the plugin, thanks for helping me, and thanks for the ninja-fast response.

As I read this

• no client would be "subscribed" (no messages sent on) until it had sent through the .emit('active', true);
• and once that has happened, other messages would be passed like normal like .emit('sent', 'yup this is sent');
• until .emit('active', false); is sent in by this client

is that correct?

Brainstorming

If mine is an edge case, this should be a sufficient workaround.

The concept of "listening = true/false" seems like a simple enough one to implement (perhaps a slightly cleaner implementation than your above code, but functionally the same). It isn't as versatile/direct as customizing the publish/subscribe, but it is a heck of a lot easier and simpler.

If you think customizing the publish/subscribe "rules" for notifications is a common enough use case, perhaps you could provide default publish/subscribe, allowing developers to manually assign if they had custom rules. (?) Or maybe you could look for a streams.subscribe() method, which could be run on the client to determine if it should subscribe. (?)

from meteor-streams.

Yes you are correct. You've to do allow write permissions also. If emited from a client

Notifications.permissions.read(function() {
  return true
});

Your suggestion on the API is good. I'll consider it 👍
I'm thinking about new easy to understand API. I'll publish more info as I go through it.

from meteor-streams.