[Alsaplayer-devel] More things to do: adding controlling via TCP-socket and splitting main app

[Andy Lo A Foe]

Hi,

This was my big plan before I became bogged down :-)

All the work to achieve this is mostly done, check the daemon "interface"..

BTW I'm really glad to see new life in the project!

For now.. back to lurker mode...

Gr,
Andy

On 3/8/07, Peter Lemenkov <lemenkov at gmail.com> wrote:
> Hello All!
>
> AlsaPlayer can be driven via Unix-socket using libalsaplayer. I think
> that is a generally good idea - to create a TCP-based interface (and
> move libalsaplayer to  standalone application and adding crossplatform
> capabilities if they're absent).
>
> My vision of future of AP is main daemon (completely free of any
> interface-modules) driven by standalone interfaces via unix-sockets or
> tcp (possibly udp?). MPD has similar strategy but it has also some
> flaws (for example poor concept of media-database and very limited
> number of input formats).
>
> Summarizing things, here is a list of my ideas:
>
> * Adding TCP-based control module in parallel with unix-socket based one.
> * Separating libalsaplayer and checking for crossplatform-readiness
> * Separating all interfaces (the main questionable thing).
>
> I'd like to discuss these things fbefore starting actual work )
> --
> With best regards!
>
> _______________________________________________
> alsaplayer-devel mailing list
> alsaplayer-devel at lists.tartarus.org
> http://lists.tartarus.org/mailman/listinfo/alsaplayer-devel
>