Re: [Jack-Devel] ladish + jack autoconnect

On Sat, Dec 31, 2011 at 10:51 AM, Robin Gareus <[hidden]> wrote:
> On 12/25/2011 12:22 AM, Nedko Arnaudov wrote:
> [..]
>> Now that I think of it, I dont recall proposing to implement this option
>> for jack1. So here I do it:
>>
>> I'd like to implement new jack1 server option (exposed in jackd too) with
>> value that defaults to current behaviour. The option (kind of enum) has
>> four other possible values. In total:
>>
>>  * dont restrict self connect attempts (default)
>>  * ignore (dont fail, nop) all self-connect requests
>>  * fail all self-connect requests
>>  * ignore self connect requests to other clients only
>>  * fail self connect requests to other clients only
>>
>> If something in my proposal is not clear, please let me know. I'll try
>> to clarify it.
>
> ..now that the mailing-list and jackaudio.org infrastructure is working
> fine again..
>
> would the jack-maintainers care to comment on this proposal?

i've had this discussion with nedko on IRC before i stopped being
prepared to discuss things with him (and why would i do that? "the
entire JACK API has been shit right from the start". no need to
discuss that further then).

the proposal has some merits i think. i don't think its very useful
for most use cases, but in some reasonably likely ones, some of these
options would be very useful to have. it would integrate quite well
with JACK Session, and enables that and ladish to do what they want
without having to modify clients, which is a good thing. but ... to be
actually useful, i suspect that this option needs to be controllable
in a running server, not just at startup.

1325347409.3788_0.ltw:2,a <CAFa_cKkAANvBOx1uH6rBe3ASz9w=k=ZoQS7chnO5jchDyG8-QA at mail dot gmail dot com>