Angus Leeming <[EMAIL PROTECTED]> writes:
| On Monday 19 August 2002 2:30 pm, Lars Gullik Bjønnes wrote:
>> | Anyway, I'm perfectly happy to use named sockets rather than pipes, but
>> | AFAICS there is still a problem. If I'm an external program, how do I
>> | find out the /name/ of this named socket if LyX is going to have many of
>> | them. Without this info I can't even start.
>>
>> .lyx/server-socket.1234
>> .lyx/server-socket.4634
>> .lyx/server-socket.P
>>
>> Every instance of LyX will only have _one_ socket.
>
| This seems reasonable. It looks to me like we can use André's pipestream
| class today. Excellent. Future Windows support will follow by enhancing
| Pipestream. LyX will know nothing about it.
>
| As a bit of fun, a shell client would presumably ascertain which LyX socket
| to connect to like this (below).
Remember that a socket could be stale...
--
Lgb
