Commit History

GIT Hash	Branch	Date	Author	Log Message
61204490 [view]	master	2005-12-07 18:35:48 +0000	dscho	[libtdevnc] plug memory leaks
6a7736f8 [view]	master	2005-12-07 18:30:22 +0000	dscho	[libtdevnc] translate keys based on unicode (much more reliable than sym)
54906d73 [view]	master	2005-11-28 16:30:47 +0000	runge	[libtdevnc] x11vnc: add -loop option.
8eb18f6c [view]	master	2005-11-25 07:22:43 +0000	runge	[libtdevnc] fix deadlock from rfbReleaseExtensionIterator(), fix no libz/libjpeg builds, disable tightvnc-filetransfer if no libpthread, add --without-pthread option, rm // comments, set NAME_MAX if not defined, x11vnc: throttle load if fb update requests not taking place.
de99644d [view]	master	2005-10-23 04:11:28 +0000	runge	[libtdevnc] configure.ac: test ... == ... not allowed on all unix.
30c00d0b [view]	master	2005-10-23 03:29:38 +0000	runge	[libtdevnc] x11vnc: -filexfer, -slow_fb, -blackout noptr,...
94d7fc84 [view]	master	2005-10-07 10:06:54 +0000	dscho	[libtdevnc] update TODO
951ec26b [view]	master	2005-10-07 09:58:45 +0000	dscho	[libtdevnc] The PseudoEncoding extension code was getting silly: If the client asked for an encoding, and no enabled extension handled it, LibVNCServer would walk through all extensions, and if they promised to handle the encoding, execute the extension's newClient() if it was not NULL. However, if newClient is not NULL, it will be called when a client connects, and if it returns TRUE, the extension will be enabled. Since all the state of the extension should be in the client data, there is no good reason why newClient should return FALSE the first time (thus not enabling the extension), but TRUE when called just before calling enablePseudoEncoding(). So in effect, the extension got enabled all the time, even if that was not necessary. The resolution is to pass a void** to enablePseudoEncoding. This has the further advantage that enablePseudoEncoding can remalloc() or free() the data without problems. Though keep in mind that if enablePseudoEncoding() is called on a not-yet-enabled extension, the passed data points to NULL.
2c177c86 [view]	master	2005-10-06 22:17:40 +0000	dscho	[libtdevnc] update ChangeLog for today
194a76df [view]	master	2005-10-06 19:26:41 +0000	dscho	[libtdevnc] add an extension mechanism for LibVNCClient, modify the client data handling so that more than one data structure can be attached, and add an example to speak the client part of the back channel.

GIT Hash

Branch

Date

Author

Log Message

61204490 [view]

master

2005-12-07 18:35:48 +0000

dscho

[libtdevnc] plug memory leaks

6a7736f8 [view]

master

2005-12-07 18:30:22 +0000

dscho

[libtdevnc] translate keys based on unicode (much more reliable than sym)

54906d73 [view]

master

2005-11-28 16:30:47 +0000

runge

[libtdevnc] x11vnc: add -loop option.

8eb18f6c [view]

master

2005-11-25 07:22:43 +0000

runge

[libtdevnc] fix deadlock from rfbReleaseExtensionIterator(), fix no libz/libjpeg builds, disable tightvnc-filetransfer if no libpthread, add --without-pthread option, rm // comments, set NAME_MAX if not defined, x11vnc: throttle load if fb update requests not taking place.

de99644d [view]

master

2005-10-23 04:11:28 +0000

runge

[libtdevnc] configure.ac: test ... == ... not allowed on all unix.

30c00d0b [view]

master

2005-10-23 03:29:38 +0000

runge

[libtdevnc] x11vnc: -filexfer, -slow_fb, -blackout noptr,...

94d7fc84 [view]

master

2005-10-07 10:06:54 +0000

dscho

[libtdevnc] update TODO

951ec26b [view]

master

2005-10-07 09:58:45 +0000

dscho

[libtdevnc] The PseudoEncoding extension code was getting silly:
If the client asked for an encoding, and no enabled extension handled it,
LibVNCServer would walk through all extensions, and if they promised to handle
the encoding, execute the extension's newClient() if it was not NULL.
However, if newClient is not NULL, it will be called when a client connects,
and if it returns TRUE, the extension will be enabled. Since all the state of
the extension should be in the client data, there is no good reason why
newClient should return FALSE the first time (thus not enabling the extension),
but TRUE when called just before calling enablePseudoEncoding().
So in effect, the extension got enabled all the time, even if that was not
necessary.
The resolution is to pass a void** to enablePseudoEncoding. This has the
further advantage that enablePseudoEncoding can remalloc() or free() the
data without problems. Though keep in mind that if enablePseudoEncoding()
is called on a not-yet-enabled extension, the passed data points to NULL.

2c177c86 [view]

master

2005-10-06 22:17:40 +0000

dscho

[libtdevnc] update ChangeLog for today

194a76df [view]

master

2005-10-06 19:26:41 +0000

dscho

[libtdevnc] add an extension mechanism for LibVNCClient, modify the client data handling
so that more than one data structure can be attached, and add an example
to speak the client part of the back channel.