Right.  The thing @xaiki pointed is right to, but I made there an ugly hack
because is a method that will dissapear.  I dont see the point of making
more efforts into this since @fabriciocosta's code is the one that should
implement the command queue in the right way.  I made it non-blocking and
provided a place where the "processQueue" method should be called (now it
just calls "playPlaylists").  I think if I put more code into this, it will
be harder for him to replace this code.


2013/4/10 Tomas Neme <notifications@github.com>

> In mosto.js:
>
> > @@ -150,14 +161,13 @@ function mosto(configFile) {
> >
> >      console.log("mbc-mosto: [INFO] Starting mbc-mosto... ") ;
> >
> > -    self.startMvcpServer(function() {
> > -        self.startWatching();
> > -        self.initDriver();
> > -    });
> > +    self.startMvcpServer();
> > +    self.startWatching();
>
> I think these are correct like this. Once the inits are run, mosto will
> just start getting it's callbacks called, right?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/inaes-tic/mbc-mosto/pull/39/files#r3745711>
> .
>