[ecasound] JACK port naming [patch]

On Tue, Sep 9, 2008 at 12:31 AM, Kai Vehmanen <kvehmanen@email-addr-hidden> wrote:
> Personally, I'm leaning towards to accepting the patch. Ecasound's JACK code
> was developed during very early days of JACK (in 2001-02), and at that time
> it was far from clear how people would end up using the system. Things like
> "jack_alsa" look a bit dated now, and I think "jack_generic" suffers partly
> from the same design rot. I agree that if someone needs to use
> "jack_generic" (versus e.g. "jack"), it is likely she would appreciate
> predictable port numbering as well.

Could we deprecate jack_alsa?

What I'm missing is some combination of jack_auto and jack_generic.
like jack_generic,local_portprefix,remote_client or
jack_auto,remote_client,local_portprefix.

And why not give jack and jack_generic the same options, deprecate
jack_generic (but keep it available for some more years) and simplify
everything to:

jack
jack,local_portprefix
jack,local_portprefix,remote_client

jack_auto
jack_auto,remote_client

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Ecasound-list mailing list
Ecasound-list@email-addr-hidden
https://lists.sourceforge.net/lists/listinfo/ecasound-list
Received on Tue Sep 9 12:15:01 2008