Ok, thought it would be nice to have this, but didnt know about the publish
issue.  Leave it this way if you thing it will give us no problem!


2013/4/10 Tomas Neme <notifications@github.com>

> In drivers/playlists/mongo-driver.js:
>
> >
> >          self.scheds = db.collection('scheds');
> >          self.lists = db.collection('lists');
> > -        self.readPlaylists();
> > +
> > +        // these two lines must go, mosto will take care of calling these
> > +        var boundaries = self.validTimes();
> > +        self.readPlaylists(boundaries.from, boundaries.to);
> >
> >          channel.subscribe({channel: 'schedbackend', method: 'create'}, function(msg) {
>
> actually, that channel there needs to be changed to backend so that's
> there
>
> The thing is that this is NOT different channels. For one, mubsub's
> message queue is unique, there's no channels, there's filtering by message
> content (NOT the redis default, which is filtering by channel, but a nice
> addendum), and the caspa bit publishes all messages on the same function
> with something like: channel.publish({channel: channel, method: method,
> model: model}), so using different functions would be complicated for
> publishing.
>
> I *could* provide some auxiliary functions or constants, but think that
> there's going to be a "schedules create", "schedules update", "schedules
> read", "schedules delete", "medias create", "medias update"........ the
> backend (schedbackend here, but there's others) name is already repeated
> in some spaces, like in the Backbone models and/or views
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/inaes-tic/mbc-mosto/pull/38/files#r3746476>
> .
>