Ideas for X improvement.

David Jackson djackson452 at gmail.com
Thu May 26 12:29:42 PDT 2011


The client wouldnt have to be moved between servers at all, it could be the
same proxy server, the proxy server could then open up connections to actual
X servers and forward things to the real X servers. The proxy would massage
and rework data as necessary to trick the X client and hide the fact it is
being displayed to many X servers and also keep the X servers in the dark
about what is really going on as well. This requires no protocol changes and
no changes to the clients or servers. There are already two or more
codebases that this has already been done on, one is something called Xmux,
the other was something called Xshare or something, and I am aware of a
possible third that was called XTV. None are actively developed at this
time.

On Thu, May 26, 2011 at 11:26 AM, Glynn Clements
<glynn at gclements.plus.com>wrote:

>
> David Jackson wrote:
>
> > I am know C, however I know little about X internals or X protocol. Is
> there
> > a good source of documentation that would give a person a full
> introduction
> > and overview of how the X server works,including how it all fits
> together,
> > and a tour of the system and documentation of the internals such as
> > functions, variables etc? Basically everything need for a person who only
> > knows C to learn all about how the X server works?
>
> How a specific implementation works doesn't really matter, as that's
> something which can be changed. What can't be changed (without
> breaking compatibility) is the protocol.
>
> The relevant documentation can be found here:
>
>        http://www.x.org/releases/X11R7.6/doc/
>
> The main thing to bear in mind is the client-server model. If you want
> to migrate a connection to a different X server, you either have to
> ensure that the new X server will behave exactly like the old one, or
> make the client adjust to the change. The former is somewhere between
> ridiculously difficult and completely impossible, while the latter
> requires significantly changing the protocol, libraries, toolkits, and
> applications.
>
> --
> Glynn Clements <glynn at gclements.plus.com>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg/attachments/20110526/7fce49ae/attachment.html>


More information about the xorg mailing list