linuxaudio.org

--20cf3074b01e609f8004c0b448c7

Content-Type: text/plain; charset=ISO-8859-1
On Wed, May 23, 2012 at 3:30 PM, Nikita Zlobin  wrote:
> What things, you think, may need to create such all-purpose API?
What is the use case for "Per client time wheel management." ?

What is the use case for "Waiting wheel. ?"
Unless these represent common uses of JACK, the required features have no

role in the API. Currently, these look like corner cases to me.
It it true that I skipped over the proposal for dynamic/on-the-fly backend

switching. This has already been discussed and yes, it would be great to

add it. Torben did this for his "tschak" implementation. Its another

example of something that needs to be done, not discussed.
> As for

quoted text
> rooms - it is just a side effect of what i propose. JACK api doesn't

> need to be changed; way to select jack instance by client may be same

> as today. I'm not sure even, that you read message up to end -

> including proposed structure.

>

I did read it to the end, which is why I remarked on the port metadata idea

which would make the "rooms" idea much easier to implement and manage

efficiently.
--20cf3074b01e609f8004c0b448c7

Content-Type: text/html; charset=ISO-8859-1

Content-Transfer-Encoding: quoted-printable
On Wed, May 23, 2012 at 3:30 PM, Nikita =

Zlobin <cook60020tmp@mail.ru> wrote:

What things, you think, may need to create such all-purpose API?What is the use case for "Per client time wheel management.=

" ?What is the use case for "Waiting wheel. ?"

Unless these represent common uses of JACK, the required features have no r=

ole in the API. Currently, these look like corner cases to me.It it=

 true that I skipped over the proposal for dynamic/on-the-fly backend switc=

hing. This has already been discussed and yes, it would be great to add it.=

 Torben did this for his "tschak" implementation. Its another exa=

mple of something that needs to be done, not discussed.

=A0 As for

rooms - it is just a side effect of what i propose. JACK api doesn't

need to be changed; way to select jack instance by client may be same

as today. I'm not sure even, that you read message up to end -

including proposed structure.I did read it to the=

 end, which is why I remarked on the port metadata idea which would make th=

e "rooms" idea much easier to implement and manage efficiently.

=A0
--20cf3074b01e609f8004c0b448c7--