Re: [Jack-Devel] RFC: jackd portnames

On Thu, Nov 03, 2011 at 05:41:15PM -0400, Paul Davis wrote:
 
> 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?

Where is the API to use that generic message passing mechanism.
Jack Session may be using some generic low level mechanisms, but
those are not exposed and available for arbitrary message types.
That makes it ad-hoc.


Ciao,

-- 
FA

Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.

1320357100.14045_0.ltw:2,a <20111103215059.GD22868 at linuxaudio dot org>