Hi!
Adding a few new protocol numbers (MD5 hash and TurboVNC pseudo-encodings).
Cheers,
Peter
commit 284d0b37ee9d0de47e37f962ccfa6bad3fc9ac0b
Author: Peter Rosin p...@lysator.liu.se
Date: Thu Oct 8 19:46:28 2009 +0200
Add new protocol numbers (MD5 auth and TurboVNC pseudo-encodings
Den 2009-09-01 10:21 skrev Pierre Ossman:
Steer things towards UTF-8, whilst also adding a notice that
historically there has been a lot of different encodings in use.
Signed-off-by: Pierre Ossman oss...@cendio.se
Yes, please.
Cheers,
Peter
Den 2009-08-17 12:47 skrev Adam Tkac:
On Mon, Aug 17, 2009 at 11:20:08AM +0200, Peter Rosin wrote:
Den 2009-08-17 10:59 skrev Adam Tkac:
On Mon, Aug 17, 2009 at 10:22:56AM +0200, Peter Rosin wrote:
If it is so natural with UTF-8 and if it really is the only sane choise
(I think it is), it's
Den 2009-08-17 11:45 skrev Peter Åstrand:
No we didn't, we agreed on that for the desktop name.
Refresh my memory - which other strings are sent as ANSI CODE PAGE?
Username and password in the VeNCrypt extension. There are some strings
in the gii extension. The tight file transfer extension
commit 017aa8439b2855792e0ba47092d4354fc26ac064
Author: Peter Rosin p...@lysator.liu.se
Date: Tue Jun 16 14:11:11 2009 +0200
Describe the Tight LastRect Pseudo-encoding.
Signed-off-by: Peter Rosin p...@lysator.liu.se
diff --git a/rfbproto.rst b/rfbproto.rst
index 33a8fc5
commit bd46a9f54ae8c3ff5a6d4566a3332d4cf3e8ac77
Author: Peter Rosin p...@lysator.liu.se
Date: Tue Jun 16 14:24:30 2009 +0200
Describe the Tight Encoding.
Signed-off-by: Peter Rosin p...@lysator.liu.se
diff --git a/rfbproto.rst b/rfbproto.rst
index 9db6164..24aab00 100644
Den 2009-05-29 16:38 skrev Pierre Ossman:
On Fri, 29 May 2009 12:51:48 +0200
Peter Rosin p...@lysator.liu.se wrote:
The only drawback I can think of is that some server might
not respond at all to empty update requests, even if non-
incremental, and then you'd end up not nowing if you have
Hi Pierre,
Den 2009-05-28 13:34 skrev Pierre Ossman:
The implementation of the DesktopSize (also called NewFBSize)
pseudo-encoding differs a bit between VNC families. This tries to
document a behaviour that works in the majority of the implementations.
Signed-off-by: Pierre Ossman
Also add some introductory text to each chapter involving gii.
Signed-off-by: Peter Rosin p...@lysator.liu.se
diff --git a/rfbproto.rst b/rfbproto.rst
index 18cda39..dfea980 100644
--- a/rfbproto.rst
+++ b/rfbproto.rst
@@ -81,7 +81,7 @@ example, a pen-based handwriting recognition engine might
Den 2009-05-15 12:20 skrev Pierre Ossman:
On Thu, 14 May 2009 15:56:35 +0200
Peter Rosin p...@lysator.liu.se wrote:
Den 2009-05-11 13:27 skrev Pierre Ossman:
That sounds a bit like this look like crap, but pff, what do I
care? :)
Well, that's stretching it, but exactly one person has
Den 2009-05-15 11:24 skrev Pierre Ossman:
It seems we agree that implementations should be done in a way that
supports everything, we just need to agree on a wording that conveys
that. :)
Indeed :-)
On Thu, 14 May 2009 15:04:27 +0200
Peter Rosin p...@lysator.liu.se wrote:
Den 2009-05-11
Den 2009-05-11 13:24 skrev Pierre Ossman:
On Tue, 05 May 2009 11:53:27 +0200
Peter Rosin wrote:
That doesn't solve anything though. I would like my implementation to
be compatible with both the spec and the wilderness. Tightening the
spec after the fact does not achieve that goal
Describe the zlibhex encoding in terms of the hextile encoding.
Signed-off-by: Peter Rosin p...@lysator.liu.se
(I'm not all satisfied with the double^Wtripple reference to zlib...)
Cheers,
Peter
diff --git a/rfbproto.rst b/rfbproto.rst
index 896fb8b..363d0d0 100644
--- a/rfbproto.rst
+++ b
13 matches
Mail list logo
