Hmm. I agree that it makes sense to put the dynamic playlist functionality
into a proxy daemon. Especially with the ability to add arbitrary data to
tracks.
What about the search feature though? Should the daemon continually poll
and cache all of mpd's library in order to provide that search? I think it
makes sense to put that in mpd.
On Mon, Jan 23, 2012 at 3:13 AM, Max Kellermann <m...@duempel.org> wrote:
> On 2012/01/23 12:08, Andy Kelley <superjo...@gmail.com> wrote:
> > Hi,
> >
> > I fixed http://www.musicpd.org/mantis/view.php?id=3423
> >
> > Also, I have a question. I'm forking mpd, with the goals below in mind.
> My
> > question is, does it *have* to be a fork, or is this compatible with your
> > roadmap?
>
> Does it have to be MPD features? All of this can easily be
> implemented in an accompanying daemon that other clients can
> communicate with over the new client-to-client protocol, without
> bloating the MPD core with very special features.
>
> Max
>
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Musicpd-dev-team mailing list
Musicpd-dev-team@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
