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

On 30 November 2011 16:28, Paul Davis <[hidden]> wrote:
> 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.
>

Ah, OK.  I think I was naively expecting the lib had it's own
communication channel with the server.

>> 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.

I was just going to specify that the new version of JNAJack will not
work with versions of JACK below that - the mapping will immediately
fail because it can't find jack_free.  The workaround if needed would
be to use the existing version of JNAJack, which I'll keep available.
Of course, I may need to look at a more robust way of mapping
'optional' functions as JNAJack develops!

Thanks,

Neil


-- 
Neil C Smith
Artist : Technologist : Adviser
http://neilcsmith.net

1322673956.22305_0.ltw:2,a <CAHvRSodJAvBTZmDMUz0WEvB9=1A_DjrkxSZDjxk+OLYgZRc_Zg at mail dot gmail dot com>