Xref: utzoo comp.windows.x:36021 comp.windows.open-look:1351
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnews!djb
From: djb@cbnews.cb.att.com (david.j.bryant)
Newsgroups: comp.windows.x,comp.windows.open-look
Subject: XDM??
Keywords: XDM, X Terminals
Message-ID: <1991May3.203305.5000@cbnews.cb.att.com>
Date: 3 May 91 20:33:05 GMT
Followup-To: comp.windows.x
Organization: AT&T Bell Laboratories
Lines: 29


I've seen an occasional article go by regarding the use of XDM with
X terminals, but admit to not being very familiar with XDM.  Before I go
off and try and puzzle it out, how widely used is XDM?

In particular:
	1) How widespread is its use in general?  Do the great majority of
	   X terminal users rely on it?  If I'm going to buy and use
	   X terminals, do I need to have XDM available in order for them
	   to be maximally useful?
	2) Do commercial X terminal manufacturers encourage or require
	   XDM?  Since I buy my X Window System environments from vendors
	   (e.g. Sun, HP, AT&T), should I be hammering on them to support
	   XDM so I can make good use of my X terminals?
	3) What X terminal and/or X Window System vendors (if any) 
	   support XDM?

I'm willing to dive into XDM in anticipation of getting an X terminal, but
don't know whether it's vital, preferred, nifty, useful-but-unnecessary, or 
just an interesting alternative for connecting X terminals to the rest of my
environment.

	Thanks in advance,
					 UUCP: att!cbosgd!djb
	David Bryant                           att!cborion!djb
	AT&T Bell Laboratories       INTERNET: djb@cborion.cb.att.com
	Room 1B-256                            djb@cbosgd.att.com
	6200 East Broad Street          PHONE: (614) 860-4516
	Columbus, Ohio  43213             FAX: (614) 868-4302