Skip to content

Evaluate correct naming for internal clients (which are not drivers) #63

Open
@dvzrv

Description

@dvzrv

It seems the (unwritten?) convention about internal clients vs. drivers appears to be, that the drivers have a jack_ prefix and the internal clients do not.
Both types of shared object files usually (on Linux) live below e.g. /usr/lib/jack/.

With jack2 <= 1.9.20 and jack-example-tools we provide jack_inprocess.so, jack_internal_metro.so and jack_intime.so. If these are not in fact drivers, they should be renamed (stripped of their jack_ prefix).

Somewhat related and more of a discussion topic:
Would it make sense to have a specific prefix for all internal clients (e.g. internal_), so that they can be clearly distinguished?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdocumentationImprovements or additions to documentationquestionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions