Dirk Meyer wrote: > Jason Tackaberry wrote: >> I seem to recall that opinion involving greatly simplifying (or >> removing) the state engine. > > The state engine now uses coroutines, it _should_ be safe to remove > the state decorator. But it _could_ break code depending on it.
Well, let me say something more: to the outside it looks that way. You can call 'yield open()' and it will be finished when the backend is open. But in the inside we still call backend.open() and what for the backend to change the state. This is the old code I don't like at all. IMHO backend.open() should return an InProgress object that will be called when the backend is open. Since our backends are based on external processes some kind of state machine would be required at this point. Dischi -- "I've not lost my mind. It's backed up on tape somewhere." - Unknown ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
