Subject: Re: [ecasound] standalone ECI implementations
From: Tony Leake (tony_leake_AT_hotmail.com)
Date: Sat Sep 28 2002 - 08:48:17 EEST
+1 I really like this idea. From PHP's viewpoint I'm sure
more people would be interest if they don't have to compile anything and can
just include a pre built class file.
>I know, I know, I still haven't finished the NetECI project and here I
>am again with new ideas... ;)
>Tkeca-0.2.1, which btw is a really usable app, uses ecasound by forking
>the console interface on the background and then piping commands and
>replies via stdin and stdout.
>Compared to using ECI or directly linking against libecasound, this
>approach has the huge benefit of complete independence from ecasound
>libraries. In practice, just by renaming the ecasound executable (or
>changing PATH), I can select between ecasound 2.0.4 and 2.1dev12 (CVS).
>Tkeca-0.2.1 works nicely with both versions!
>Now what if all ECI apps would use the same mechanism? This could be
>achieved by making a new C-implementation of the ECI API, which would do:
>- fork "ecasound -c" to the background
>- pass ECI commands to the ecasound instance via its stdin
>- read the return codes from ecasound's stdout, parse them and
> pass them to the ECI app
>... that's about it. The C++, Python, Perl and PHP ECI implementations
>could either use the C implementation or alternatively provide their own
>implementation. For instance, a Python ECI implementation could be
>written totally in Python. This means that no extension modules would
>need to installed. Just a Python interpreter and the ecasound executable
>and that's it!
> Audio software for Linux!
>To unsubscribe send message 'unsubscribe' in the body of the
>message to <ecasound-list-request_AT_wakkanet.fi>.
Chat with friends online, try MSN Messenger: http://messenger.msn.com
This archive was generated by hypermail 2b28 : Sat Sep 28 2002 - 08:47:01 EEST