Path: utzoo!attcan!uunet!husc6!bloom-beacon!ZERMATT.LCS.MIT.EDU!RWS
From: RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler)
Newsgroups: comp.windows.x
Subject: Sun's NeWS/X merge
Message-ID: <19880614205407.1.RWS@KILLINGTON.LCS.MIT.EDU>
Date: 14 Jun 88 20:54:00 GMT
References: <2791215666-2624871@Sierra>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 29


    Date: Mon, 13 Jun 88  12:41:06 CDT
    From: Kerry Kimbrough <Kimbrough@dsg.csc.ti.com>

    Does anyone know exactly this works?

There was a talk on the subject at the 1988 X Conference, and there
will be a paper on the subject presented at the upcoming Usenix.

    Can a client alternately send either X or
    NeWS protocol over a single connection?

No.  I believe at present the protocols remain "native", on
separate connections.

    Are the basic objects common to both X and NeWS?

For the most part, yes.

    That is, can I freely convert between an X window and a NeWS window,

Yes.

    an X event and a NeWS event, etc.?

This is a little trickier, and I don't remember the details.
As I recall, at the base are NeWS events, and there is an X
input thread that expresses interest in NeWS events and
converts and dispatches them to X clients appropriately.