On 6/28/06, Roman Shaposhnick <[EMAIL PROTECTED]> wrote:
On Wed, Jun 28, 2006 at 10:46:29AM -0700, Russ Cox wrote:
> Over the weekend I shuffled things around. Instead of
> linking X code into every program, there is now a single
> program, called devdraw, that contains X interface code.
> Graphical programs now fork and exec a devdraw and then
> speak a simple protocol to its standard input and standard
> output to read from the keyboard and mouse and draw on the
> screen. Devdraw is not a threaded program. It runs on the
> standard system stack and uses select(2) to manage its two
> inputs. It uses only a single connection to the X server.
> My hope is that doing things the Official Unix Way inside
> devdraw will eliminate the problems people have reported.
This sounds interesting enough, but what's the "language"
an application is supposed to talk to devdraw binary in ?
Is it just the draw(3) ?
Thanks,
Roman.
I'd think you're still supposed to talk in draw(3) for portability's
sake right? :-)
Some protocols don't have to be fully open, but it might be
interesting to know about them.
Dave
