tpf@jdyx.UUCP (Tom Friedel) (10/18/89)
The 386/ix implementation of X11R3 uses a shared memory region for server/client communication if the socket emulation library is not installed. I have to believe that shared memory is the most efficient solution to this problem. Has anyone placed such code in the public domain? Tom -- Tom Friedel (404) 320-7624 tpf@jdyx.UUCP CIS: 71131,3234 also: tpf@jdyx.atlanta.ga.us ...gatech!emory!jdyx!tpf Public Access Unix BBS: (404) 321-5020 "Live simply, so that others may simply live."
klee@chico.pa.dec.com (Ken Lee) (10/18/89)
In article <1989Oct17.191614.10659@jdyx.UUCP>, tpf@jdyx.UUCP (Tom Friedel) writes: > I have to believe that shared memory is the most efficient solution to > this problem. > > Has anyone placed such code in the public domain? A few shared memory X transports have been floating around, but all have problems. For several reasons, shared memory is not as great as it seems: 1. memory still isn't that cheap 2. the semaphors (or whatever) used as controls are expensive 3. many of the Xlib algorithms (e.g., graphics batching) get more complicated I'm not saying that shared memory can't work well. It's just not easy. Ken Lee DEC Western Software Laboratory, Palo Alto, Calif. Internet: klee@decwrl.dec.com uucp: uunet!decwrl!klee