« Return to Thread: [proposal] connection veto callback

Re: [proposal] connection veto callback

by Nedko Arnaudov :: Rate this Message:

Reply to Author | View in Thread

Glynn Clements <glynn@...> writes:

> Nedko Arnaudov wrote:
>
>> Disconnect veto is needed too.
>
>> We need veto callback unregistration too.
>
> I'm not sure how useful this would be; you can't veto a client
> exit()ing.

It is useful when bisbehaving client disconnects ports that are
connected by LASH during session load.

> FWIW, I agree that X window managers are the appropriate model.
>
> One client gets to be the final arbiter of all connections. If a
> supervisor exists, any connection attempt becomes a request which is
> reported to the supervisor.
>
> The supervisor may make the requested connection, reject the request,
> or make the connection to an alternative port (redirection).
>
> Redirection would allow a "dumb" client which automatically connects
> to the first two hardware ports to be connected at a more appropriate
> point in the graph, and to allow redirection to "null" ports if you
> don't want to allow the client to participate but don't want it to
> quit due to an error (e.g. playing a video when you don't need the
> sound).
Yup. :D

--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>


_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

attachment0 (194 bytes) Download Attachment

 « Return to Thread: [proposal] connection veto callback