Re: [Linuxsampler-devel] liblscp: A LinuxSampler Control Protocol implemetation

[Rui N. C. <rn...@rn...>]

Christian Schoenebeck wrote:
>
> I'm still wondering why so many people use the abbreviation 'al.' for
> 'alii'.  Kind of academic tradition? :)
>

;-)

>> A couple of weeks ago I've sent here a note about my early LSCP
>> (LinuxSampler Control Protocol) implementation, which I've named
>> liblscp.
>>
>> I've been kind of idle while waiting for comments about it,
>> before going any further, into GUI development that is.
>>
>> You can check it out from:
>>
>>     http://www.rncbc.org/ls/
>
> Seems to be down. Could you send me your current tarball?
>

Yep, it was down for quite an hour or so. The damn UPS just decided to
shutdown my server gracefully, but everything is now powered up as it
should.

Anyway, please find it here on attachment.

> Rui, I would like to split liblscp: completely removing the server side
> part from liblscp and move it directly into the LS engine codebase, so
> that liblscp is a convenient library for LS frontends only. I think this
> separation would make sense, because neither does LS need the client
> side of the lib, nor does any other application (LS frontend or
> whatever) need a 'server side' of LSCP.
>

OK, these are the only files that are server specific: lscp_server.h and
lscp_server.c (pretty obvious huh? :). Following this fashion,
lscp_client.h and lscp_client.c are the client frontends. All the rest are
common to both sides.

> Would you accept that Rui?
>

Of course. As I said, the current liblscp implementation is rather crude
and is just kind of some proof-of-concept. Nothing more.

Cheers.
-- 
rncbc aka Rui Nuno Capela
rn...@rn...