Angus Leeming <[EMAIL PROTECTED]> writes:
| Joao Luis Meloni Assirati wrote:
| > Okay, but it helps if the client was spawned by lyx, which case will be
| > the most frequent.
|
| If the client was spawned by lyx then named pipes are not needed at all. See
| the code in src/ispell.C for an example of non-named pipes. We should
| create a class similar to LyXComm (src/lyxserver.C) that performs the
| necessary book-keeping. LyXServer itself should be able to communicate with
| pipes and sockets wrapped up inside classes derived from LyXComm.
I wan thinking of an idea where the LyXServer only was able to talk
with sockets. And then have a LyXPipeProxy that creates pipes and
communicates with this socket.
The the lyx code would only have to handle sockets and the code should
be a bit simpler.
--
Lgb
