Angus Leeming <[EMAIL PROTECTED]> writes:
| On Wednesday 11 September 2002 2:39 pm, Lars Gullik Bjønnes
| wrote:
| > This is how I think this should be done.
|
| > lyx<->lyxserver--localsocket--pipesocket(as a socketclient)
| > \
| > socketclient
| >
| > what I mean is that the localsocket is the native interface,
| > and to named pipe is just built on top of this.
| >
| > There should be no need to special case pipes _inside_ lyx, it
| > is better off as an external program/daemon.
| >
| > then lyx need only to handle the localsocket (or unix socket)
| > properly.
|
| welll I have lyx<->lyxserver<->pipestream
Yes, but as said earlier: pipestream and effectively only have one
client at a time whereas a localsocket listener can have many.
and a pipestream (to get a namedpipe) can be attached to a localsocket
(a small python script/daemon should be able to do that)
--
Lgb
