Le 23 avr. 07 à 14:07, Paul Davis a écrit :
> I'm about ready to wrap up the v1.0 API by adding port
aliases which i
> believe will serve two purposes:
>
> 1) they are generally useful
> 2) they will allow us to migrate away from the
current
> backend-specific names in favor of something more
generic, without
> breaking any client behaviour
>
> my only dilemma is the best way to implement them. i
don't want to
> do a
> client/server roundtrip to lookup aliases, which means
they need to
> live
> in shared memory. this suggests (to me) 2
possibilities:
>
> a) a new shared memory "chunk" that
contains a list of aliases
> b) add a fixed number of alias slots to the existing
port structure
>
> (b) is a bit of a kludge, and limits the aliases per
port BUT at the
> same time it avoids more substantive changes to the
overall design in
> favor of a bit more memory allocation. and in reality,
the number
> of aliases per port is likely to be zero, one or two at
the outside.
>
> (a) is cleaner but requires that each client attaches
to a new shared
> memory segment and adds another set of cleanup
responsibilities to
> jackd.
>
> i also wonder how well either of these will fit with
jackdmp.
>
> comments?
>
> --p
>
The design of jackd and jackdmp in quite similar at this
level, so I
think either choice will be simple/complex for each
implementation.
Stephane
------------------------------------------------------------
-------------
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-devel lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jackit-dev
el
|
