On 04/04/2012 03:55 PM, rosea.grammostola wrote:
i may have missed it, but those application clients which are NOT coded
as compliant to a session protocol are not the point--that's just a SM
implementation convenience outside of the bounds of the "ideal-SM"
i'll refresh your memory that pyjacksm (a JSM reference implementation)
does that too (something called exo-clients or wtf:). ladish have been
doing that also and way, way before, for ages now o.O
unfortunately, i reckon, qjackctl doesn't. on my own call it has been
pure&strict to the JS business (aka. protocol) and nothing more.
however, re. exo-/infra-clients (or w/e they've been called, i don't
quite remember exactly but those are about clients which are
non-jack-session-aware) are in the drawer ntl.
actually, i was minding about the *intrinsic* cost/benefits of the
session protocol and *not* about *any* particular *session management*
rncbc aka Rui Nuno Capela
Linux-audio-dev mailing list