Re: [Jack-Devel] RFC: jackd portnames

PrevNext  Index
DateThu, 03 Nov 2011 17:41:15 -0400
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToFons Adriaensen <[hidden] at linuxaudio dot org>
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToFons Adriaensen Re: [Jack-Devel] RFC: jackd portnames
Follow-UpFons Adriaensen Re: [Jack-Devel] RFC: jackd portnames
Follow-UpFons Adriaensen Re: [Jack-Devel] RFC: jackd portnames
On Thu, Nov 3, 2011 at 5:34 PM, Fons Adriaensen <[hidden]> wrote:
> On Thu, Nov 03, 2011 at 10:31:26AM -0400, Paul Davis wrote:
>
>> I agree with the general goal here. The conflict I see is between
>> using this as the push to implement a more general feature that JACK
>> could really use, or just adopting a more fix-the-particular-problem
>> approach that this patch represents.
>
> I agree 100% with that comment on its own merits and not in particular
> w.r.t. to the portnames issue. It's just a big shame that the same
> attitude wasn't taken in other cases. Such as for the Jack Session
> patch. In that case, some completely ad-hoc extensions were accepted
> instead of going for a generic non-RT message passing mechanism wich
> could have been the base layer for a session management protocol based
> on it. Two measures and weights ? Based on what ?

Jack Session precisely uses the EXISTING generic, non-RT message
mechanism that has been in the JACK server from the beginning. Perhaps
you just want a DIFFERENT generic, non-RT message mechanism in the
server. There was no special hack to add it, other than some new
message types, which are going to have to exist at some level no
matter what mechanism is used.

the session manager uses the exact same message passing mechanism that
all other JACK clients use when they want the server to do something.
its not the world's greatest protocol, but its certainly nothing
specifically to do with jack session, or any other specific part of
the JACK API.

cf.

typedef enum  {
  BufferSizeChange,
  SampleRateChange,
  AttachPortSegment,
  PortConnected,
  PortDisconnected,
  GraphReordered,
  PortRegistered,
  PortUnregistered,
  XRun,
  StartFreewheel,
  StopFreewheel,
  ClientRegistered,
  ClientUnregistered,
  SaveSession,                <<<<<<<< JACK Session
  LatencyCallback
} JackEventType;

where is this "ad hoc extension" other than this new message type?
PrevNext  Index

1320356513.13571_0.ltw:2,a <CAFa_cKnSVhH_YTW6OhLAQiFC0KkSWjBwcK6uKQrOn-OdN6zahQ at mail dot gmail dot com>