xtrans

[Alan Coopersmith]

Adam Jackson wrote:
> On Wednesday 11 May 2005 11:09, Soeren Sandmann wrote:
> 
>>Adam Jackson wrote:
>>
>>>That's exactly what's done in xlibs, though Soeren's email wasn't
>>>completely clear:
>>
>>Well, not *exactly*, but my mail wasn't completely clear. Alan is
>>proposing to put them in /usr/lib/X11/xtrans.  Note the /lib/.   In
>>xlibs they are put in /usr/include/X11/xtrans.
> 
> 
> Oop, didn't see the lib part.  Yes, includes under /usr/include please.

For includes we want people to use I agree.   I was simply thinking the
harder this is to find, the less people will attempt to use it.   I suppose
/usr/include/X11/xtrans with a warning in the README and header files would
do just as well.

> Do any such components exist outside of xc/ ?
> 
> It's a template for talking to the socket layer in an abstract fashion.  This 
> seems to limit its use to the libs, the server, and a few proxies (xrx, 
> lbxproxy, xfs, and xfwp, seems to be the full set).  We don't install it in 
> the SDK currently, so if it is being used externally to xc then that app 
> already has a copy.

The xscope in Solaris uses xtrans as well, since it's also a proxy, and that
was the easiest way to add IPv6 support.   (Which reminds me, it would be 
nice for xscope to appear on freedesktop.org somewhere - perhaps in the 
proposed contrib section of the modular tree? - since we've got changes we
can contribute to X.Org, but would need to slog through a separate legal
review from Sun's lawyers to contribute it to anyone but X.Org.)

-- 
	-Alan Coopersmith-           alan.coopersmith at sun.com
	 Sun Microsystems, Inc. - X Window System Engineering