Angus Leeming <[EMAIL PROTECTED]> writes: > > Lars Gullik BjÃnnes wrote: > > Actaully this wouldn't be _that_ hard, it is all about having a nice > > protocol between the gui and the core. I guess I could do it in a > > week. This also fits quite well with some other cleanup that I'd > > really like to do, but there are problems as well... security is one. > > I'm sure that this is only one part of the whole, but have you had a look > at http://giallo.sourceforge.net/ for a library to handle the sockets or > named pipes in a platform independent way? My understanding is that this > is slated to become Boost.Sockets eventually.
Just to keep you going: what do you two plan for the undo function? A central undo queue on the server which is shared by all users or individual queues for each client which are synchronized into a consistent server state? What about the buffer? I think the lyx-paragraphs should be on the server but the cursor position at the client (I dont know the current code too well, maybe they are already separated) There should be a consensus that all included files must be on the server; for temporary files it might be necessary to copy them to a client local /tmp directory which should be a straightforward extension of the new Mover. Well, I think we could have a *lot* of fun with this feature, it would be unfair if Lars uses it all up in one week ;-) /Andreas
