Paul Davis wrote:
> On Mon, 2007-04-23 at 17:09 +0100, Rui Nuno Capela
wrote:
>
>> shm cache indirection should suffice,... but that
would break 0.x ABI, I
>> think :/
>
> no clients are ever permitted access to any JACK data
structures. this
> does not break any ABI. libjack is the big fat
insulating layer here.
>
Yes, current API won't change, but some new handles are
forthcoming. or not?
>> what I mean is that literal string names should
_not_ ever
>> beeen in shared mem, just some kind of handles/ids,
mapped to outside
>> .conf/.ini/registry/properties file or whatever.
Yeah...just a quick thought
>
> we have the port and client names in shared mem? what'
the issue?
>
I was actually thinking, wrongly perhaps, in getting rid of
literal
client and port name strings being resident on shm. Some
kind of hashed
associative array instead, uh?
>> I'm also edging on doing the qjackctl migration
dance towards Qt4, so
>> doing something like so... disruptive, would come
at hand, eh eh  ~
>
> always aiming to please the customer
>
I'm sure ain't the only one ;)
--
rncbc aka Rui Nuno Capela
rncbc rncbc.org
------------------------------------------------------------
-------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and
take
control of your XML. No limits. Just data. Click to get it
now.
http://sourcefor
ge.net/powerbar/db2/
_______________________________________________
Jackit-devel mailing list
Jackit-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jackit-dev
el
|
