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

Well ? Are you see any problem / risk in approach where jack_get_ports will just "hide" inactive ports (.. or ports owned by inactive clients, whatever ;-)

--
Pawel

Dnia Pi±tek, 1 Marca 2013 15:00 Pawel <[hidden]> napisa³(a) 
> Dnia Pi±tek, 1 Marca 2013 14:26 Stéphane Letz <[hidden]> napisa³(a) 
> > 
> > Le 1 mars 2013 ? 14:05, Pawel <[hidden]> a écrit :
> > 
> > > Hi,
> > > 
> > > I made small test app for test inactive port connection issue. I just tested Jack2 and it is also affected by this problem.
> > > 
> > > When you execute it , you can observe that Jack server say:
> > > Cannot connect ports owned by inactive clients: "TEST" is not active
> > > 
> > > .. while jack_get_ports still see it. Both Jack1 and Jack2 are affected.
> > > 
> > > Please found it in attachment.
> > > 
> > > I have two ideas:
> > > 1) jack_connect should return some predefined king of error (like EEXISTS)
> > > ... or ..
> > > 2) jack_get_ports shouldn't return inactive ports (this is more reliable IMHO).
> > 
> > This is no "inactive" ports but rather "inactive" applications.
> OFC .. this was shorthand - inactive app have inactive ports .. it matter how we call such ports ?
> 
> > > 
> > > Compile:
> > > gcc -g -o test test.c -ljack
> > > 
> > > Regards
> > > Pawel
> > > 
> > I'm not sure we can "afford" to change this kind of behavior, since this may break a lot of existing clients. 
> > 
> > Stéphane
> 
> My first suggestion was "safe way" it doesn't break anything, but second is IMHO more correct.
> 
> There would be also "jack_client_is_active" call for connect managers (for mark inactive ports).
> 
> Pawel
> 
> 
> 
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

1362643915.17631_0.ltw:2,a <51384bc333aff6.15159645 at wp dot pl>