Subject: Re: [linux-audio-dev] Re: timing issues in a client/server enviroment
From: David Olofson (audiality_AT_swipnet.se)
Date: la loka 09 1999 - 22:13:44 EDT
On Sun, 10 Oct 1999, Benno Senoner wrote:
[...]
> Hmm, I partly disagree, because the DAW app has provide all the audio server
> functionality.
> there are 2 solutions:
> 1) the app implements his own "server" which is rather silly since you are
> reinventing the wheel.
Actually, the idea is that serving clients shouldn't be all that
different from hosting plug-ins. (The communication is asyncronous,
at least to some extent, as opposed to done through a callback.) And
if you have the client/server port for communication anyway, it should
basically be a matter of implementing the init events that clients
will send when they want to use your services. Or; clients and
servers are pretty similar.
> 2) the app calls our audio server, but then we are in my proposed case.
> :-)
Well, there's the client side of the API, if you want to hack some
cool bonus features (read: server) in as well. :-)
//David
PS. This isn't looking complex, is it? ;-)
·A·U·D·I·A·L·I·T·Y· P r o f e s s i o n a l L i n u x A u d i o
- - ------------------------------------------------------------- - -
·Rock Solid David Olofson:
·Low Latency www.angelfire.com/or/audiality ·Audio Hacker
·Plug-Ins audiality_AT_swipnet.se ·Linux Advocate
·Open Source ·Singer/Composer
This archive was generated by hypermail 2b28 : pe maalis 10 2000 - 07:27:13 EST