messages, and callback-function that will be called with the messages.
When you want to send, use "send()".
This class encapsulates all the dirty communication and thus provides
messages, and callback-function that will be called with the messages.
When you want to send, use "send()".
This class encapsulates all the dirty communication and thus provides
public:
/** When we receive a message, we send it to a client.
This is one of the small things that would have been a lot
cleaner with a Signal/Slot thing.
*/
public:
/** When we receive a message, we send it to a client.
This is one of the small things that would have been a lot
cleaner with a Signal/Slot thing.
*/
- LyXComm(LString const &pip, LyXServer * cli, ClientCallbackfct ccb = 0)
- :pipename(pip), client(cli), clientcb(ccb)
- {
+ LyXComm(string const & pip, LyXServer * cli, ClientCallbackfct ccb = 0)
+ : pipename(pip), client(cli), clientcb(ccb) {
- void send(LString const &);
+ void send(string const &);
+
+ /// We receive messages via XForms through this callback
+ static void callback(int fd, void *v);
+
// how it will be done for 0.12. In 0.13 we must write a non-gui
// bufferview.
// IMO lyxserver is atypical, and for the moment the only one, non-gui
// bufferview. We just have to find a way to handle situations like if
// lyxserver is using a buffer that is being edited with a bufferview.
// With a common buffer list this is not a problem, maybe. (Alejandro)
// how it will be done for 0.12. In 0.13 we must write a non-gui
// bufferview.
// IMO lyxserver is atypical, and for the moment the only one, non-gui
// bufferview. We just have to find a way to handle situations like if
// lyxserver is using a buffer that is being edited with a bufferview.
// With a common buffer list this is not a problem, maybe. (Alejandro)
- LyXServer(LyXFunc *f, LString const &pip)
- : numclients(0), func(f), pipes(pip, (this), callback)
- { }
+ ///
+ LyXServer(LyXFunc * f, string const & pip)
+ : numclients(0), func(f), pipes(pip, (this), callback) {}