>> > or >> > should i just go email GlassElevator and see what stirs when this is >> > poured into the mix? :) >> I was going to that by myself, but I have to look at RDP/VNC/X first. > >Maybe Fresco (http://www.fresco.org) has some interesting aspects, too? I sometimes read their mailing-lists and they are writing some new network code to get a good and portable communication layer (CORBA, etc. were not good enough). >Possibly we could reuse their code (license is LGPL, so there is no big problem here, is it)? >Maybe we could even replace the R2/3 app_server with Fresco? But one step after the other... > >Waldemar > A couple of approaches to distributing BMessages have been taken that I know of: In 1996 I developed BMorb (http://www.halcyon.com/jrashmun/ bmorb.html), which consists of a class derived from BMessenger, a file type that contains only attributes, and a daemon to do the routing, and somewhat later, Jeremy Friesner developed MUSCLE (http://www.bebits.com /app/962), which, when I last looked at it, was a good deal more intrusive into the development process, but is supported on non-BeOS systems. Jeremy won a prize of chocolate chip cookies (from Jon Watte, or was it Marco?) for his demo using MUSCLE for remote desktop control, probably in 1997 or 1998. Regards, John