Xref: utzoo comp.windows.x:7421 comp.os.vms:11234 comp.sys.dec:966
Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!tut.cis.ohio-state.edu!accelerator.eng.ohio-state.edu!kcgl1.eng.ohio-state.edu!JONESD
From: JONESD@kcgl1.eng.ohio-state.edu (David Jones)
Newsgroups: comp.windows.x,comp.os.vms,comp.sys.dec
Subject: Re: DECwindows: does it use DECnet, TCP or both?
Message-ID: <1505@accelerator.eng.ohio-state.edu>
Date: 20 Jan 89 03:08:23 GMT
References: <2774@stiatl.UUCP>
Sender: news@accelerator.eng.ohio-state.edu
Organization: Ohio State University
Lines: 21

The key to determining how easily third party TCP/IP packages can be
integrated into DECWindows depends upon how DEC did the interface to
the VMS X server. If the interface employs a pseudo-device driver that
simply passes the X11 protocol stream to/from the server via QIO's, it's a
trivial problem.  A pseudo-device that merely provides graphics primitives
would make writing your own network interface much more difficult.

If the DECWindows interface uses the latter method but provides a library
for protocol conversion on the server side (the client side has it or
no one would be able to write applications), then a roll-your-own network
server is doable with a fair amount of work.

Is there anybody who has worked with the DECWindws development kit who
can comment on this (the product has been announced, after all!).

David L. Jones               |      Phone:    (614) 292-6929
Ohio State Unviversity       |      Internet:
1971 Neil Ave. Rm. 406       |               jonesd@kcgl1.eng.ohio-state.edu
Columbus, OH 43210           |               jones-d@eng.ohio-state.edu

Disclaimer: A repudiation of a claim.