David Jackson djackson...@gmail.com writes:
As far as I know NX is a tunneling and compression technology but will
not maintain a persistant X applications or session. The applications
are started when you connect from a remote location.
NX, along with compression and caching technologies,
sorry i was wrong
On Sat, May 28, 2011 at 2:35 AM, Evgeny M. Zubok evgeny.zu...@tochka.ruwrote:
David Jackson djackson...@gmail.com writes:
As far as I know NX is a tunneling and compression technology but will
not maintain a persistant X applications or session. The applications
are
I have recently started running x11vnc on an Xrfb server. This pretty much
seems to solve my problems I had with Xvnc. Xvnc did not support render. It
appears xrfb does and that konqueror runs fine on Xrfb, it would not run on
Xvnc. So now I just run Xrfb and then x11vnc on that, and that gives me
Alan Coopersmith wrote:
http://en.wikipedia.org/wiki/Xpra
http://code.google.com/p/partiwm/wiki/xpra
This is the VNC approach (render locally, forward raster data), but
done on a window-by-window basis using compositing.
As such, it suffers from most of the same problems as x11vnc
Glynn Clements gl...@gclements.plus.com writes:
AFAICT, the only advantage is rootless operation.
That is quite large advantage. My largest problem with VNC is that
switching workspaces is slow since it needs to redraw everything.
However, xpra is not usable for me due to keyboard layout
rootless operation is a big advantage in certain cases. But you are right,
it does not forward any vector graphics data, such as GLX commands, which
probably are somewhat faster than rasterised data. Currently, i am using
xpra and x11vnc on Xvfb. When you use x11vnc on Xvfb, it seems to work much
I meant to say, xvfb. not xrfb. The xvfb and x11vnc combo works great and is
better than Xvnc. So far it has fixed my problems with not being able to use
konqueror on VNC.
On Sat, May 28, 2011 at 8:35 AM, David Jackson djackson...@gmail.comwrote:
I have recently started running x11vnc on an
On 05/28/11 08:49 AM, David Jackson wrote:
xvnc did not support render,
There are multiple Xvnc programs out there. The RealVNC one everyone
used to use has been abandoned by its authors in favor of their commercial
product, and is still built on an ancient XFree86 4.3. Other open source
On 05/28/2011 07:22 AM, Evgeny M. Zubok wrote:
David Jackson djackson...@gmail.com writes:
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
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
David Jackson wrote:
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
On 05/26/11 12:29 PM, David Jackson 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
Thank you for the information. As I mentioned, I was previously aware of
Xmx, Xmove and XTV..
On Fri, May 27, 2011 at 11:44 AM, Alan Coopersmith
alan.coopersm...@oracle.com wrote:
On 05/26/11 12:29 PM, David Jackson wrote:
The client wouldnt have to be moved between servers at all, it could
THanks for the info on XPRA. I will give it a try. It looks promising and
the way they use the compositing manager sounds genius. It sounds like they
get basically final rasterised data from the compositor, so basically it
seems like a huge bitmap, if I am correct. Or maybe I am not.
If hardware
On Thu, May 26, 2011 at 2:18 PM, David Jackson djackson...@gmail.com wrote:
I was not able to find any documentation on a VNC loadable module anywhere.
Is there a place where one can find out about this?
My build was based on these instructions:
On 05/28/2011 12:39 AM, David Jackson wrote:
THanks for the info on XPRA. I will give it a try. It looks promising
and the way they use the compositing manager sounds genius. It sounds
like they get basically final rasterised data from the compositor, so
basically it seems like a huge bitmap,
This advice is valid for all software projects. if you want people to help
develop software, document the software code with documentation. Explain how
the parts of the software fit together, how the code operates, explain what
the different parts do, document functions and variables and what each
On 05/27/11 04:43 PM, David Jackson wrote:
This advice is valid for all software projects. if you want people to help
develop software, document the software code with documentation. Explain how
the
parts of the software fit together, how the code operates, explain what the
different parts
David Jackson djackson...@gmail.com writes:
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
As far as I know NX is a tunneling and compression technology but will not
maintain a persistant X applications or session. The applications are
started when you connect from a remote location.
As far as X peristant session, an up to date XVNC that supports Render would
probably be fine a
On
I like VNC and have built both loadable module and DDX version.
The main problem with the DDX version is that since VNC
has a GPL license I can not merge the code into my Xorg
source tree.
Pat
---
On Wed, May 25, 2011 at 6:07 PM, David Jackson djackson...@gmail.com wrote:
On Wed, May 25,
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
I was not able to find any documentation on a VNC loadable module anywhere.
Is there a place where one can find out about this?
On Thu, May 26, 2011 at 7:34 AM, Pat Kane pekan...@gmail.com wrote:
I like VNC and have built both loadable module and DDX version.
The main problem with the DDX
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
X.org needs to listen to users on X Window System flexibility. X has
always been about mechanism, not policy, that allows users choice and
flexibility, such as in window manangers. Many people I talk to, including
myself, find remote desktop capabilities extremly useful and greatly
increase the
On 05/25/11 12:53 PM, David Jackson wrote:
X.org needs to listen to users on X Window System flexibility.
X.Org does listen, but we don't have developers sitting around with nothing to
do, but instead have far more things to work on than people volunteering to work
on them.
A display driver
/me trudges through the rest
On Wed, May 25, 2011 at 12:53 PM, David Jackson djackson...@gmail.com wrote:
Backwards compatability is always a must. It has become clear that X
graphics primatives today are outgrown today by some applications today
which have intense graphics needs. Current X
X Server is a complex piece of software and thus there are complex issues
involved with its implementation that warrant the message length. I did put
most of my concerns in this message so there is not much more I need to add.
The message is not that long though, its not a 50 page technical
On Wed, May 25, 2011 at 3:07 PM, Alan Coopersmith
alan.coopersm...@oracle.com wrote:
On 05/25/11 12:53 PM, David Jackson wrote:
X.org needs to listen to users on X Window System flexibility.
X.Org does listen, but we don't have developers sitting around with nothing
to
do, but instead
David,
Try TigerVNC not TightVNC. Although I cant see documentation... I did
find this quote
TigerVNC is an advanced VNC implementation. It is based on the fourth
generation of VNC. TigerVNC also includes features from the TightVNC
and TurboVNC projects. This includes accelerated JPEG
On 05/25/11 01:54 PM, David Jackson wrote:
I looked for information on vnc.so on Tightvnc's website.
Tiger, not Tight, and yes, their website doesn't publish the documentation for
their software, complain to them.
There are no
instructions or documentations there on how one would even use it.
David Jackson wrote:
A display driver that contains a VNC server. The problem with x11vnc is that
it is slow, very slow. XVnc server, which is a X server that contains a VNC
server but has no hardware drivers, is much faster since the VNC server is
built directly into the X server,
What
On Wed, May 25, 2011 at 4:30 PM, Alan Coopersmith
alan.coopersm...@oracle.com wrote:
On 05/25/11 01:54 PM, David Jackson wrote:
I looked for information on vnc.so on Tightvnc's website.
Tiger, not Tight, and yes, their website doesn't publish the documentation
for
their software, complain
I seemed to be missing the patch you obviously meant to attach.
Dave.
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address:
On Wed, May 25, 2011 at 4:36 PM, Glynn Clements gl...@gclements.plus.comwrote:
David Jackson wrote:
A display driver that contains a VNC server. The problem with x11vnc is
that
it is slow, very slow. XVnc server, which is a X server that contains a
VNC
server but has no hardware
35 matches
Mail list logo
