On 1/28/2011 1:30 PM, Max Kellermann wrote: > On 2011/01/28 17:24, Tim Carter<t...@frontierdigital.com> wrote: >> I had considered making the controller responsible for maintaining >> persistent play history but I'm trying to limit it's role to >> 'fire-and-forget' and allow MPD to do what it does best; play the >> music. This separation also contributes to the robustness of the >> system as playback is not dependent on the controller; if the >> controller goes pear-shaped MPD just keeps on playing the last thing >> it was told to do -- nice. > The system would not depend on the controller; MPD can play music fine > on its own, and will just continue playback of the queue even when the > controller is gone. The controller just adds features on top, like > eliminating duplicates automatically. Well, in the event the queue empties playback would stop. Under my current model (load playlist, set repeat, walk away) the last loaded playlist just continues to play without interruption.
Your point is taken. T. ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
