Re: [Jack-Devel] Graph callback and client state

PrevNext  Index
DateTue, 09 Apr 2013 22:16:40 +0200
From Stéphane Letz <[hidden] at grame dot fr>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
Ccjack-devel <[hidden] at lists dot jackaudio dot org>
In-Reply-ToPaul Davis Re: [Jack-Devel] Graph callback and client state 
Le 9 avr. 2013 à 21:51, Paul Davis <[hidden]> a écrit :

> 
> 
> On Tue, Apr 9, 2013 at 3:33 PM, Harry van Haaren <[hidden]> wrote:
> On Tue, Apr 9, 2013 at 7:45 PM, Stéphane Letz <[hidden]> wrote:
> > You can never be sure that ports returned by jack_get_ports are always valid
> 
> Any chance that adding a flag,  "JackPortIsActive" to JackPortFlags allows the functionality to be implemented?
> On activation, the JACK server marks all of the client owned ports as "active".
> Patchbay managers etc call jack_port_flags() and can query if its an "active" port or not?
> 
> there is always a race ... sometime between when you get the ports and when you use the information, ports could be added, removed or become inactive.


This is more or less my point : "ports could be added, removed or become inactive."  Inactive state is not so specific… so why bother to treat this case only? This racy API cannot be corrected.

Stéphane
PrevNext  Index

1365538615.15122_0.ltw:2,a <AC37E91F-337B-4D8B-9FBA-3694C239C1BC at grame dot fr>