Re: [Jack-Devel] jack_free from when? and a couple of other things

PrevNext  Index
DateWed, 30 Nov 2011 11:28:22 -0500
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToNeil C Smith <[hidden] at neilcsmith dot net>
Ccjack-devel <[hidden] at lists dot jackaudio dot org>
In-Reply-ToNeil C Smith Re: [Jack-Devel] jack_free from when? and a couple of other things
Follow-UpNeil C Smith Re: [Jack-Devel] jack_free from when? and a couple of other things
On Wed, Nov 30, 2011 at 11:09 AM, Neil C Smith <[hidden]> wrote:

> I just want to document why that parameter is required.  Initially
> (and possibly naively) it seemed superfluous.  Taking a stab in the
> dark at answering my own question, can I assume it's there because
> it's possible to have multiple servers running and the lib needs to
> know which server to ask to connect ports on?

have you ever seen a server/client API that did not use such a data
structure? the jack_client_t contains information required to
communicate with the client. we don't want to open a new connection to
the server every time a request is made.

> btw - don't suppose you've got a Jack1 version number for jack_free support?

i do ... 0.118.3 ... but this just highlights (again) another major
issue with JACK right now - the absence of a defined soname that
identifies the API rather than the version or implementation. it would
be best if you could avoid version number testing if at all possible -
this has already caused issues in some other JACK clients.
PrevNext  Index

1322670605.16231_0.ltw:2,a <CAFa_cK=QJbGXKAGvZRp81_ZG_SZ2T3fhcR1tAVrqdaZ3SdXdLA at mail dot gmail dot com>