[rfbproto] Clarify lifetime rules for Hextile fg and bg colors

Hi! Tristan Richardson said he was going to update the Internet Draft with this clarification of the Hextile encoding in a private response to a direct question from me. Cheers, Peter commit 6aa46f7e824de21f5374c989cb2c13a580685dc9 Author: Peter Rosin Date: Thu Oct 8 19:59:07 2009 +0200

[rfbproto] New protocol number

Hi! Adding a few new protocol numbers (MD5 hash and TurboVNC pseudo-encodings). Cheers, Peter commit 284d0b37ee9d0de47e37f962ccfa6bad3fc9ac0b Author: Peter Rosin Date: Thu Oct 8 19:46:28 2009 +0200 Add new protocol numbers (MD5 auth and TurboVNC pseudo-encodings) Signed-off-by

[rfbproto] Align table in ServerInit message

Hi! Found a minor whitespace glitch. Cheers, Peter commit c9317c1dea69cf46f4e832da63379cd3e03fda3c Author: Peter Rosin Date: Thu Oct 8 09:23:29 2009 +0200 Align ServerInit table. diff --git a/rfbproto.rst b/rfbproto.rst index 33b035f..6aa15c9 100644 --- a/rfbproto.rst +++ b

[rfbproto] TRLE Encoding

the ZRLE description. Cheers, Peter commit 6ddabeffa4b5d865c8d570082c9c3368d64201e7 Author: Peter Rosin Date: Thu Oct 8 19:23:02 2009 +0200 Adapt TRLE description from the Internet draft. Signed-off-by: Peter Rosin diff --git a/rfbproto.rst b/rfbproto.rst index 33b035f..515224f

Re: [rfbproto] Hextile ambiguity

Den 2009-09-07 17:41 skrev James Weatherall: > Hi Peter, > > [snip] >>> If I remember correctly, the Hextile encoding allows a tile may >> choose to "inherit" the foreground colour from the previous tile only >> if the prior tile actually had a foreground colour. The previous tile >> must therefo

Re: [rfbproto] Hextile ambiguity

Den 2009-09-07 15:10 skrev James Weatherall: > Hi Peter, > > [snip] >> However, existing implementations render the dot in the 4th tile >> with color 0x45, i.e. the last color used in the colored subrects >> tile (the 3rd tile). >> >> The spec says nothing about colored subrects touching the >> fo

[rfbproto] Hextile ambiguity

Hi List, The spec for Hextile talks about how the foreground color is carried over from the previous tile unless the ForegroundSpecified bit is set. But I have found that most existing (client) implementations change the foreground color if you feed it colored subrects. Example with four tiles 0

[rfbproto] Internet-Draft

Hi gang, just found this: http://tools.ietf.org/html/draft-levine-rfb-02 Cheers, Peter -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and d

Re: [rfbproto] [PATCH] Specify UTF-8 for strings (v2)

Den 2009-09-01 11:08 skrev Pierre Ossman: > There are still a couple of string issues remaining: > > - SecurityResult doesn't mention encoding for reason-string. It should >probably be ASCII though, which is what is specified for >reason-string in Security. Generate ASCII, hope for UTF-8

Re: [rfbproto] [PATCH] Specify UTF-8 for strings (v2)

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 Yes, please. Cheers, Peter --

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

Den 2009-08-20 10:22 skrev Pierre Ossman: > Can we please try to find some middle ground here. Is this text > acceptable to everyone: Yes, ok with me. Thanks! Cheers, Peter -- Let Crystal Reports handle the reporting - F

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

Den 2009-08-17 15:57 skrev Peter Åstrand: > On Mon, 17 Aug 2009, Peter Rosin wrote: > >> And I'd say they are all in the "protocol", just not in our >> specification of the protocol, so it's still a problem in my book. >> If we add this language now, we

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

Den 2009-08-17 15:24 skrev Peter Rosin: > 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 pass

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

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 tr

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

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 real

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

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 enough if our spec says (e.g.) >>>>

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

Den 2009-08-17 09:00 skrev Peter Åstrand: > On Fri, 14 Aug 2009, Peter Rosin wrote: > >>> Besides, didn't we agree on that there is no such server that sends >>> strings with the "ANSI CODE PAGE"? >> >> No we didn't, we agreed on that fo

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

Den 2009-08-12 15:13 skrev Peter Åstrand: > On Wed, 12 Aug 2009, Peter Rosin wrote: > >> Huh? If an existing client treats the incoming desktop name as if it >> is in the ansi code page (I think most Windows clients do effectively >> that), and our spec says that it MUST t

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

Den 2009-08-12 13:42 skrev Peter Åstrand: > On Wed, 12 Aug 2009, Peter Rosin wrote: > >>>> If we say MUST or even SHOULD, anyone encountering something >>>> else will get the feeling that fingerpointing is prefectly >>>> valid. It is not, and we can'

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

led "UTF-8". If one side doesn't support UTF-8 strings it means >> that strings will be in old format (which effectivelly means >> unspecified encoding). If both sides declare that they support UTF-8 >> all strings will be sent in UTF-8. We should also declare tha

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

Den 2009-08-12 11:05 skrev Peter Åstrand: > On Mon, 27 Jul 2009, Peter Rosin wrote: >> My take on this is that you (Cendio?) wants to say "all strings >> MUST/SHOULD be UTF-8 unless otherwise specified". I don't get >> why you feel that there is need f

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

Den 2009-06-25 16:42 skrev Peter Åstrand: > On Thu, 25 Jun 2009, Peter Rosin wrote: > >> If we don't enforce an extension mechanism for this, there will be no >> way to be compatible with old style (basically ASCII) and new style >> (UTF-8) without user settings. Re

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

Den 2009-06-29 11:16 skrev Pierre Ossman: > On Fri, 26 Jun 2009 21:15:40 +0200 > Peter Rosin wrote: > >> Den 2009-06-25 16:26 skrev Pierre Ossman: >>> Incompatible is a term that will have to be used loosly here. There is >>> no compatibility here today as every

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

Den 2009-06-29 09:07 skrev Peter Åstrand: > On Fri, 26 Jun 2009, Peter Rosin wrote: > >>> Without a poll or something like that we'll never know how many uses >>> "strange" desktop names today, but my guess is that it's something >>> like

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

Den 2009-06-25 16:26 skrev Pierre Ossman: > Incompatible is a term that will have to be used loosly here. There is > no compatibility here today as everyone is doing different things, so I > don't see this move making things any worse. I never answered this, so here I go. I'd be happier if it was

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

Den 2009-06-25 18:39 skrev Peter Åstrand: > On Thu, 25 Jun 2009, Peter Rosin wrote: > >>> I'm not sure how their version will affect anything. Given the history, >>> you can never be sure that this field will display correctly when using >>> anything othe

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

Den 2009-06-25 16:26 skrev Pierre Ossman: > On Thu, 25 Jun 2009 15:38:09 +0200 > Peter Rosin wrote: > >> I don't want this, sorry. This is an incompatible change. I think we >> need to go with the common denominator (which is ASCII), then use some >> kind of exten

Re: [rfbproto] [PATCH] Specify UTF-8 for strings

Den 2009-06-25 14:50 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 > --- > > Index: rfbproto.rst > ===

[rfbproto] [PATCH] Describe the DesktopName pseudo-encoding. v2

Description derived from a message on the vnc-list: http://www.realvnc.com/pipermail/vnc-list/2008-January/058496.html Signed-off-by: Peter Rosin I think we decided on UTF-8 *for this text* in that other thread. So, I'm shortcutting the discussion on the bigger problem with this up

Re: [rfbproto] [PATCH 0/6] Tight: Describe various encodings. v2

Den 2009-06-17 11:46 skrev Pierre Ossman: > On Wed, 17 Jun 2009 10:46:46 +0200 > Peter Rosin wrote: > >> Hello, >> >> Some more encoding descriptions: >> >> [PATCH 1/6]: Rearrange described and registered encodings. >> [PATCH 2/6]: Describe the Tight

[rfbproto] [PATCH 6/6]: Update Tight Encoding description to match guidelines. v2

commit ad07b53fc0d8d910c502ce21b25c8c5bb0a5623a Author: Peter Rosin Date: Wed Jun 17 10:45:35 2009 +0200 Update Tight Encoding description to match guidelines. Signed-off-by: Peter Rosin diff --git a/rfbproto.rst b/rfbproto.rst index 90545a3..0fcfe2e 100644 --- a/rfbproto.rst

[rfbproto] [PATCH 5/6]: Describe the Tight JPEG Quality Level Pseudo-encoding. v2

commit 474bbee1492c8d06ebb6a9b979b1daa93aa7376d Author: Peter Rosin Date: Tue Jun 16 14:37:04 2009 +0200 Describe the Tight JPEG Quality Level Pseudo-encoding. Signed-off-by: Peter Rosin diff --git a/rfbproto.rst b/rfbproto.rst index 24aab00..90545a3 100644 --- a/rfbproto.rst

[rfbproto] [PATCH 4/6]: Describe the Tight Encoding. v2

commit bd46a9f54ae8c3ff5a6d4566a3332d4cf3e8ac77 Author: Peter Rosin Date: Tue Jun 16 14:24:30 2009 +0200 Describe the Tight Encoding. Signed-off-by: Peter Rosin diff --git a/rfbproto.rst b/rfbproto.rst index 9db6164..24aab00 100644 --- a/rfbproto.rst +++ b/rfbproto.rst

[rfbproto] [PATCH 3/6]: Describe the Tight LastRect Pseudo-encoding. v2

commit 017aa8439b2855792e0ba47092d4354fc26ac064 Author: Peter Rosin Date: Tue Jun 16 14:11:11 2009 +0200 Describe the Tight LastRect Pseudo-encoding. Signed-off-by: Peter Rosin diff --git a/rfbproto.rst b/rfbproto.rst index 33a8fc5..9db6164 100644 --- a/rfbproto.rst +++ b

[rfbproto] [PATCH 2/6]: Describe the Tight Compression Level Pseudo-encoding. v2

commit 462808803a5034bfb25b22de2630eeb3a63994dd Author: Peter Rosin Date: Tue Jun 16 14:09:52 2009 +0200 Describe the Tight Compression Level Pseudo-encoding. Signed-off-by: Peter Rosin diff --git a/rfbproto.rst b/rfbproto.rst index 6a0f94e..33a8fc5 100644 --- a/rfbproto.rst

[rfbproto] [PATCH 1/6] Rearrange described and registered encodings. v2

commit c6f9903894e980763441b3c5039ba33ec9555169 Author: Peter Rosin Date: Tue Jun 16 13:56:29 2009 +0200 Rearrange described and registered encodings. Signed-off-by: Peter Rosin diff --git a/rfbproto.rst b/rfbproto.rst index 71ad07a..6a0f94e 100644 --- a/rfbproto.rst +++ b

[rfbproto] [PATCH 0/6] Tight: Describe various encodings. v2

Hello, Some more encoding descriptions: [PATCH 1/6]: Rearrange described and registered encodings. [PATCH 2/6]: Describe the Tight Compression Level Pseudo-encoding. [PATCH 3/6]: Describe the Tight LastRect Pseudo-encoding. [PATCH 4/6]: Describe the Tight Encoding. [PATCH 5/6]: Describe the Tight

Re: [rfbproto] [PATCH 5/5]: Describe the Tight JPEG Quality Level Pseudo-encoding.

Den 2009-06-17 10:17 skrev Pierre Ossman: > On Tue, 16 Jun 2009 18:53:58 +0200 > Peter Rosin wrote: > >> The reason I'm not backing the name change is that the one registering >> the encoding gets to decide the name, IMHO. And the zywrle (ab)use >> should not i

Re: [rfbproto] [PATCH 4/5]: Describe the Tight Encoding.

Den 2009-06-16 16:35 skrev Pierre Ossman: > On Tue, 16 Jun 2009 16:22:27 +0200 > Peter Rosin wrote: > >> So, again, I think all these deficiencies should be fixed in a followup >> commit (or commits)... >> > > Fair enough. Could you prepare those changes th

Re: [rfbproto] [PATCH 5/5]: Describe the Tight JPEG Quality Level Pseudo-encoding.

Den 2009-06-16 16:37 skrev Pierre Ossman: > On Tue, 16 Jun 2009 16:24:07 +0200 > Peter Rosin wrote: > >> Den 2009-06-16 14:00 skrev Pierre Ossman: >>> And do we want to make this a generic extension? Perhaps call it "Lossy >>> Quality Level..." instead

Re: [rfbproto] [PATCH 5/5]: Describe the Tight JPEG Quality Level Pseudo-encoding.

Den 2009-06-16 14:00 skrev Pierre Ossman: > On Thu, 11 Jun 2009 13:31:09 +0200 > Peter Rosin wrote: > >> +JPEG Quality Level Pseudo-encoding >> +-- >> + >> +Specifies the desired quality from the JPEG encoder. Encoding number >

Re: [rfbproto] [PATCH 4/5]: Describe the Tight Encoding.

Den 2009-06-16 13:58 skrev Pierre Ossman: > On Thu, 11 Jun 2009 13:30:41 +0200 > Peter Rosin wrote: > >> +The least significant four bits of *compression-control* byte inform >> +the client which zlib compression streams should be reset before >> +decoding the rectang

Re: [rfbproto] [PATCH 3/5]: Describe the Tight LastRect Pseudo-encoding.

Den 2009-06-16 13:33 skrev Pierre Ossman: > On Thu, 11 Jun 2009 13:30:09 +0200 > Peter Rosin wrote: > >> +LastRect Pseudo-encoding >> + >> + >> +A client which requests the *LastRect* pseudo-encoding is declaring >> +that it does not

Re: [rfbproto] [PATCH 2/5]: Describe the Tight Compression Level Pseudo-encoding.

Den 2009-06-16 13:33 skrev Pierre Ossman: > On Thu, 11 Jun 2009 13:29:42 +0200 > Peter Rosin wrote: > >> +Compression Level Pseudo-encoding >> +- >> + >> +Specifies the desired compression level. Encoding number -247 implies

Re: [rfbproto] [PATCH 1/5]: Rearrange described and registered encodings.

Den 2009-06-16 13:28 skrev Pierre Ossman: > On Thu, 11 Jun 2009 13:28:54 +0200 > Peter Rosin wrote: > >> Rearrange described and registered encodings. >> >> Signed-off-by: Peter Rosin > > I'm not convinced this is worth it. The style of t

Re: [rfbproto] [PATCH] Describe the DesktopName pseudo-encoding

Den 2009-06-15 13:34 skrev Peter Åstrand: > On Fri, 12 Jun 2009, Peter Rosin wrote: > >>> This is certainly possible and should work. But it's a lof of work: >>> We need to specify the different cases and the new pseudo encoding, >>> all VNC implementations

Re: [rfbproto] [PATCH] Describe the DesktopName pseudo-encoding

Den 2009-06-12 10:22 skrev Peter Åstrand: > On Thu, 11 Jun 2009, Daniel P. Berrange wrote: > >>> Having a security type named UTF-8, which simply allowed the client >>> to select the "real" security type right after it would perhaps not be >>> so difficult. >> >> I've never much liked the idea of

Re: [rfbproto] [PATCH] Describe the DesktopName pseudo-encoding

Den 2009-06-11 18:06 skrev Daniel P. Berrange: > On Thu, Jun 11, 2009 at 05:00:52PM +0200, Peter Rosin wrote: >> Den 2009-06-11 12:15 skrev Daniel P. Berrange: >>> On Thu, Jun 11, 2009 at 11:15:14AM +0200, Peter Rosin wrote: >>>> Having a security type named UTF-8, w

Re: [rfbproto] [PATCH] Describe the DesktopName pseudo-encoding

Den 2009-06-11 12:15 skrev Daniel P. Berrange: > On Thu, Jun 11, 2009 at 11:15:14AM +0200, Peter Rosin wrote: >> Having a security type named UTF-8, which simply allowed the client >> to select the "real" security type right after it would perhaps not be >> so diffic

[rfbproto] [PATCH 5/5]: Describe the Tight JPEG Quality Level Pseudo-encoding.

commit ede4a75ac83718cc787d4bae4f6bae5be10fcdb2 Author: Peter Rosin Date: Thu Jun 11 13:11:51 2009 +0200 Describe the Tight JPEG Quality Level Pseudo-encoding. Signed-off-by: Peter Rosin diff --git a/rfbproto.rst b/rfbproto.rst index 2bbb39a..2fb75e8 100644 --- a/rfbproto.rst

[rfbproto] [PATCH 4/5]: Describe the Tight Encoding.

commit 37a79217907b19258f3e89593861d3ee27dee8cb Author: Peter Rosin Date: Thu Jun 11 13:08:30 2009 +0200 Describe the Tight Encoding. Signed-off-by: Peter Rosin diff --git a/rfbproto.rst b/rfbproto.rst index c6ee650..2bbb39a 100644 --- a/rfbproto.rst +++ b/rfbproto.rst

[rfbproto] [PATCH 3/5]: Describe the Tight LastRect Pseudo-encoding.

commit bd5d706f122ea82c1367459bc7064fae7fc2202f Author: Peter Rosin Date: Thu Jun 11 13:04:59 2009 +0200 Describe the Tight LastRect Pseudo-encoding. Signed-off-by: Peter Rosin diff --git a/rfbproto.rst b/rfbproto.rst index 7034d9a..c6ee650 100644 --- a/rfbproto.rst +++ b

[rfbproto] [PATCH 2/5]: Describe the Tight Compression Level Pseudo-encoding.

commit f99be43f942f43238bdc9d8badc51ac6ea97b871 Author: Peter Rosin Date: Thu Jun 11 13:03:53 2009 +0200 Describe the Tight Compression Level Pseudo-encoding. Signed-off-by: Peter Rosin diff --git a/rfbproto.rst b/rfbproto.rst index 95525c9..7034d9a 100644 --- a/rfbproto.rst

[rfbproto] [PATCH 1/5]: Rearrange described and registered encodings.

commit 9a76e63161ccc2ffa7c67e9ed42de2f8de18155c Author: Peter Rosin Date: Thu Jun 11 12:43:09 2009 +0200 Rearrange described and registered encodings. Signed-off-by: Peter Rosin diff --git a/rfbproto.rst b/rfbproto.rst index 71ad07a..95525c9 100644 --- a/rfbproto.rst +++ b

[rfbproto] [PATCH 0/5] Tight: Describe various encodings.

Hello, Some more encoding descriptions: [PATCH 1/5]: Rearrange described and registered encodings. [PATCH 2/5]: Describe the Tight Compression Level Pseudo-encoding. [PATCH 3/5]: Describe the Tight LastRect Pseudo-encoding. [PATCH 4/5]: Describe the Tight Encoding. [PATCH 5/5]: Describe the Tight

Re: [rfbproto] [PATCH] Describe the DesktopName pseudo-encoding

Den 2009-06-11 11:48 skrev Daniel P. Berrange: > On Thu, Jun 11, 2009 at 10:38:45AM +0200, Peter Rosin wrote: >> Den 2009-06-04 13:34 skrev Pierre Ossman: >>> So to summarise, the only part that has some idea of what encoding it >>> wants is the Unix client. Everything e

Re: [rfbproto] [PATCH] Describe the DesktopName pseudo-encoding

Den 2009-06-04 13:34 skrev Pierre Ossman: > On Fri, 29 May 2009 10:51:14 +0200 Pierre Ossman wrote: > >> Has anyone done a survey of how implementations treat this extension >> and the name field in the server init? If there are no existing >> implementations that prevent it, then I'd like to spec

Re: [rfbproto] [PATCH] Add Makefile

Den 2009-06-04 11:23 skrev Pierre Ossman: > On Mon, 1 Jun 2009 14:30:55 +0200 > Pierre Ossman wrote: > >> On Mon, 01 Jun 2009 13:17:17 +0200 >> Peter Rosin wrote: >> >>> Those are spelled rst2newlatex.py and rst2html.py on my system. >>> What are th

Re: [rfbproto] [PATCH] Add Makefile

Den 2009-06-01 12:55 skrev Pierre Ossman: > Targets for generating a PDF and a HTML page. > > Signed-off-by: Pierre Ossman > --- > > Index: Makefile > === > --- Makefile (revision 0) > +++ Makefile (revision 0) > @@ -0,0 +1,14 @@

Re: [rfbproto] [PATCH] Describe the xvp extension

Den 2009-06-01 11:37 skrev Pierre Ossman: > On Fri, 29 May 2009 21:41:22 +0100 > Colin Dean wrote: > >> I suggest just stick with "xvp", which is what it's been called up to >> now. After all, it could be applied to systems other than virtual >> machines, so having a name with "virtual machine"

Re: [rfbproto] [PATCH] ExtendedDesktopSize extension

Den 2009-05-29 16:38 skrev Pierre Ossman: > On Fri, 29 May 2009 12:51:48 +0200 > Peter Rosin 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

Re: [rfbproto] [PATCH] Clarify DesktopSize behaviour (v2)

Den 2009-05-29 16:33 skrev Pierre Ossman: > Aw, crap. Somehow one paragraph got lost in the patch. I'd like to > apply the following: > > Index: rfbproto.rst > === > --- rfbproto.rst (revision 3823) > +++ rfbproto.rst (worki

Re: [rfbproto] [PATCH] ExtendedDesktopSize extension

Den 2009-05-28 15:44 skrev Pierre Ossman: > On Thu, 28 May 2009 14:26:42 +0200 > Peter Rosin wrote: > >> Maybe WMVi should be documented first then, so that there is no >> window of opportunity for "bad" implementations, but it's probably >>

Re: [rfbproto] [PATCH] Describe the Tight security type

Den 2009-05-29 11:00 skrev Pierre Ossman: On Thu, 28 May 2009 21:56:24 +0200 Peter Rosin wrote: Added short text about this, changed *code* to S32 (with a note) and moved the "politics" back into the main document from the README. And some nit-picking editorials. Also diffed aga

[rfbproto] [PATCH] Describe the DesktopName pseudo-encoding

Description derived from a message on the vnc-list: http://www.realvnc.com/pipermail/vnc-list/2008-January/058496.html Signed-off-by: Peter Rosin Cheers, Peter diff --git a/rfbproto.rst b/rfbproto.rst index 55f96e7..7a25583 100644 --- a/rfbproto.rst +++ b/rfbproto.rst @@ -1373,6 +1373,7

[rfbproto] [PATCH] Fix grammar in gii Server Message description

Signed-off-by: Peter Rosin Cheers, Peter diff --git a/rfbproto.rst b/rfbproto.rst index 55f96e7..b4bc777 100644 --- a/rfbproto.rst +++ b/rfbproto.rst @@ -1314,7 +1314,7 @@ Pseudo-encoding`_. Version ~~~ -The server response from a with server *gii* capabilities to a client +The server

Re: [rfbproto] [PATCH] Describe the Tight security type

Den 2009-05-28 16:24 skrev Pierre Ossman: On Thu, 28 May 2009 15:55:02 +0200 Peter Rosin wrote: Den 2009-05-11 13:35 skrev Pierre Ossman: Why is there both a numerical code, and a string pair used to identify the extension? It seems a bit redundant. Once upon a time I asked about related

Re: [rfbproto] [PATCH] Describe the xvp extension

Den 2009-05-28 18:34 skrev DEAN C.C.: > Pierre, > > I'd be happy with that. Tristan allocated the numbers as "XVP", so > do people think we should keep this as an abbreviation, i.e. refer > to it as "XVP (virtual machine control) ...", or banish the letters > "XVP" completely? Personally, I'd vo

Re: [rfbproto] [PATCH] Describe the Tight security type

Den 2009-05-11 13:35 skrev Pierre Ossman: > Why is there both a numerical code, and a string pair used to identify > the extension? It seems a bit redundant. Once upon a time I asked about related things on the tight list: http://www.nabble.com/Tight-protocol-extension---clarification-needed-td150

Re: [rfbproto] [PATCH] ExtendedDesktopSize extension

Den 2009-05-28 15:44 skrev Pierre Ossman: > On Thu, 28 May 2009 14:26:42 +0200 > Peter Rosin wrote: > >> Maybe WMVi should be documented first then, so that there is no >> window of opportunity for "bad" implementations, but it's probably >>

Re: [rfbproto] [PATCH] Describe the Tight security type

Here's a new version or the patch, with politics moved to the README file, links added for encodings documented since last time and the previously missing extension to the SecurityResult message added. BTW, you may compare my spec with this one: http://vnc-tight.svn.sf.net/viewvc/vnc-tight/trunk/

[rfbproto] [PATCH] Don't spell out General Input Interface in every heading.

Also add some introductory text to each chapter involving gii. Signed-off-by: Peter Rosin 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 generate keyboard

Re: [rfbproto] [PATCH] ExtendedDesktopSize extension

Hi again Pierre, Den 2009-05-28 13:54 skrev Pierre Ossman: > On Tue, 19 May 2009 15:45:54 +0200 > Peter Rosin wrote: > >> Den 2009-05-15 12:20 skrev Pierre Ossman: >>> Although I didn't incorporate you changes in this extension, I have >>> been thinking

Re: [rfbproto] [PATCH] Clarify FramebufferUpdateRequest/FramebufferUpdate behaviour

Hi Pierre, Den 2009-05-28 13:58 skrev Pierre Ossman: > On Tue, 19 May 2009 15:50:47 +0200 > Peter Rosin wrote: > >> Maybe add something about the fact that it is not safe to send >> SetPixelFormat messages when you have outstanding >> FramebufferUpdateRequests? (whic

Re: [rfbproto] [PATCH] Clarify DesktopSize behaviour (v2)

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 Exc

Re: [rfbproto] [PATCH] Describe the xvp extension

Hi Colin! Den 2009-05-25 20:52 skrev Colin Dean: > Peter asked me to add details of the xvp extension, so here they are ... > > Colin So I did. Thanks very much for this contribution! Some nit-picks below inline though. Cheers, Peter > Describe the xvp pseudo-encoding and xvp message types >

Re: [rfbproto] [PATCH] Clarify FramebufferUpdateRequest/FramebufferUpdate behaviour

Den 2009-05-11 13:57 skrev Pierre Ossman: > There are some corner cases in the framebuffer update system that need > to be explicitly mentioned. > > Signed-off-by: Pierre Ossman > --- > > Index: rfbproto.rst > === > --- rfbproto.rst

Re: [rfbproto] [PATCH] Clarify DesktopSize behaviour

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 wrote: > >> De

Re: [rfbproto] [PATCH] ExtendedDesktopSize extension

Den 2009-05-15 12:20 skrev Pierre Ossman: > On Thu, 14 May 2009 15:56:35 +0200 > Peter Rosin 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'

Re: [rfbproto] [PATCH] ExtendedDesktopSize extension

Den 2009-05-11 13:27 skrev Pierre Ossman: > On Wed, 06 May 2009 12:25:12 +0200 > Peter Rosin wrote: > >> Den 2009-05-04 13:50 skrev Pierre Ossman: >>> This extension adds multi-head support to RFB, and allows the client to >>> request framebuffer and sc

Re: [rfbproto] [PATCH] Clarify DesktopSize behaviour

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

[rfbproto] [PATCH] Describe the zlibhex encoding

Describe the zlibhex encoding in terms of the hextile encoding. Signed-off-by: Peter Rosin (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/rfbprot

[rfbproto] [PATCH] Add quirk about the CPIXEL type

I once did a survey of this involving several of the major implementations, but can't really remember if I checked both little and big endian servers. I for sure did check with both little and big endian on the wire though. Signed-off-by: Peter Rosin Cheers, Peter diff --git a/rfbproto.

[rfbproto] [PATCH] Describe the zlib encoding

Describe the zlib encoding in terms of the Raw encoding. Signed-off-by: Peter Rosin (I'm not all satisfied with the double reference to zlib...) Cheers, Peter diff --git a/rfbproto.rst b/rfbproto.rst index 896fb8b..97aa0fe 100644 --- a/rfbproto.rst +++ b/rfbproto.rst @@ -1220,6 +1

[rfbproto] Describe the CoRRE encoding

Describe the CoRRE encoding in terms of the RRE encoding. Signed-off-by: Peter Rosin Cheers, Peter diff --git a/rfbproto.rst b/rfbproto.rst index 896fb8b..84937e4 100644 --- a/rfbproto.rst +++ b/rfbproto.rst @@ -1219,6 +1219,7 @@ Number Name 0 `Raw Encoding`_ 1

[rfbproto] [PATCH] Describe the Tight security type

I think this is accurate. Signed-off-by: Peter Rosin (This patch depends on links.patch sent yesterday) Cheers, Peter diff --git a/rfbproto.rst b/rfbproto.rst index 896fb8b..43534a6 100644 --- a/rfbproto.rst +++ b/rfbproto.rst @@ -294,6 +294,7 @@ Number Name 0 Invalid 1

Re: [rfbproto] [PATCH] ExtendedDesktopSize extension

Den 2009-05-04 13:50 skrev Pierre Ossman: > This extension adds multi-head support to RFB, and allows the client to > request framebuffer and screen layout changes on the server. > > Signed-off-by: Pierre Ossman Ok by me, it's your extension. But do consider my comment on the DesktopSize clarif

Re: [rfbproto] [PATCH] Add SASL security type

Den 2009-05-06 10:31 skrev Daniel P. Berrange: > On Wed, May 06, 2009 at 10:23:55AM +0200, Peter Rosin wrote: >> It is official according to: >> http://realvnc.com/pipermail/vnc-list/2008-December/059463.html >> >> I don't know why it's not in the official

Re: [rfbproto] [PATCH] Add SASL security type

Den 2009-05-06 10:23 skrev Peter Rosin: It is official according to: http://realvnc.com/pipermail/vnc-list/2008-December/059463.html I don't know why it's not in the official spec yet though. Signed-off-by: Peter Rosin --- rfbproto.rst |1 + 1 files changed, 1 insert

[rfbproto] [PATCH] Add SASL security type

It is official according to: http://realvnc.com/pipermail/vnc-list/2008-December/059463.html I don't know why it's not in the official spec yet though. Signed-off-by: Peter Rosin --- rfbproto.rst |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/rfbp

[rfbproto] [PATCH] Add links from message and encoding lists

Make it easier to navigate in hypertext versions of the document. Signed-off-by: Peter Rosin Cheers, Peter diff --git a/rfbproto.rst b/rfbproto.rst index f2876b0..5e6bc1b 100644 --- a/rfbproto.rst +++ b/rfbproto.rst @@ -292,8 +292,8 @@ The security types defined in this document are: Number

Re: [rfbproto] [PATCH] Clarify DesktopSize behaviour

Den 2009-05-04 16:25 skrev Pierre Ossman: On Mon, 04 May 2009 16:09:24 +0200 Peter Rosin wrote: Den 2009-05-04 13:49 skrev Pierre Ossman: > +The server changes the desktop size by sending a pseudo-rectangle with > +the *DesktopSize* pseudo-encoding. The update containing the >

Re: [rfbproto] [PATCH] Clarify DesktopSize behaviour

Den 2009-05-04 13:49 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 > > Index: rfb

Re: [rfbproto] [PATCH] Clarify key autorepeat behaviour

ince only the repeated "down" case allows the server to tell the > difference between automatic and manual key repeats, clarify that the > "down" repeat method is the preferred. > > Also clarify that the client should handle auto repeat because of > latency pro

Re: [rfbproto] [PATCH] Add gii extension (messages and pseudo-encoding)

Den 2009-04-30 14:36 skrev Pierre Ossman: On Thu, 30 Apr 2009 13:13:34 +0200 Peter Rosin wrote: Hi! I have included docs for the gii extension. Better than nothing? Indeed. I've been thinking of an extension to get better support for modern mice, not knowing that this already ex

Re: [rfbproto] [PATCH] Add gii extension (messages and pseudo-encoding)

Den 2009-04-30 15:44 skrev Peter Rosin: ChangeLog: Document the General Input Interface (gii) extension. Signed-off-by: Peter Rosin Oh crap, I managed to skip a couple of U16 -> EU16 changes... Here's another update and sorry for the noise. Cheers, Peter ChangeLog: Document the

[rfbproto] [PATCH] Add gii extension (messages and pseudo-encoding)

Hi! I have included docs for the gii extension. Better than nothing? Cheers, Peter Index: rfbproto.rst === --- rfbproto.rst(revision 3794) +++ rfbproto.rst(working copy) @@ -777,6 +777,276 @@ *length*``U8``