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

[Dominique Michel]

Le Thu, 8 Mar 2007 18:29:38 +0300,
"Peter Lemenkov" <lemenkov at gmail.com> a écrit :

Hi Peter,

It sound like a very good idea to me.

> 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?). 

Can you recommend me links to some documentations that explain the
technical basis of those 2 concepts (unix-sockets and tcp)?

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.
I need to learn the basis of those 2 concepts to be able to comment on this.

> * Separating libalsaplayer and checking for crossplatform-readiness
I am not sure at I understand well what you mean by separating libalsaplayer.
Do you mean, as in the beginning of you post, to do a standalone application
with libalsaplayer, something as a libalsaplayer.so that can be called by other
programs or interfaces? If so, I fully agree.

> * Separating all interfaces (the main questionable thing).
> 
It is definitely a good thing to do. It will simplify the work on the long
run. With a main daemon, all the calls will be centralized to that
daemon and will be the same from different interfaces. I don't see that as
questionable but as a complement of the main daemon approch.

Ciao,
Dominique