|
From: Christian S. <chr...@ep...> - 2003-12-30 15:22:31
|
Es geschah am Dienstag, 30. Dezember 2003 14:21 als be...@ga... schrieb: > > Would it then be better to provide the socket protocol and only > > provide a C API example implementation? > > Yes, basically define a simple communication protocol > (write sort of RFC for it) > (I'd opt for something that is HTTP-like, eg. client sends command > server exectures command and sends response (or sends only back > internal status data)). > The protocol will be used by the GUI plus we can make a few small > C examples that show you how to communicate with the engine. > That way anyone can write their own frontends, scripts etc that > communicate with LinuxSampler. Ok, seems the majority here votes for a protocol. Then I will start to write a RFC today as an initial draft for the protocol. I hope to post it tomorrow here on the list. Rui, if you still insist on a C based API, then implement it yourself right after we agreed about a final version of the protocol. But I definitely think it would be much better, easier and more convenient for you to implement the communication by using the Qt facilities (qsocket AFAIK). I don't really see much sense for you to write a C API and to bind that in your C++ GUI code. CU Christian |