Ideas for X improvement.

[David Jackson]

The code bases for the X multiplexers/proxies were actually Xmove, Xmx and
XTV. Sorry about the confusion. I gave the wrong names. Xmx was developed at
brown university. I had tried Xmove before and it works with 16 bit displays
but apparently does not work with 24 bit displays. None of them are likely
up to date to support Render, etc. The concept of being able to forward one
window and its children to be displayed inside another window on another
server is an interesting and versatile concept. The idea of these tends to
be to keep the xclient connected to the same psuedo/middleman-Xserver, which
then opens connections to destination X servers. The psuedo/middleman X
server performs manipulations to keep the xclients or the destination
xserver from knowing whats going on. The psuedo/middle-man server could be a
real server as well, with a special driver for forwarding.

On Thu, May 26, 2011 at 2:29 PM, David Jackson <djackson452 at gmail.com>wrote:

> 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/20110527/9d77cbf0/attachment.html>