f52cfa651b
add handleEventsEagerly flag (Thanks, Donald)
18 years ago
79310af7e7
x11vnc: -unixpw and -stunnel. Add clipboard to input control.
18 years ago
b7773ea6e6
Added method to get extension specific client data
18 years ago
eb08d83d62
Added method to get extension specific client data
18 years ago
d3599be1b8
add functions to unregister extensions/security types
18 years ago
880035ad54
IRIX linker is very picky about order of libraries
18 years ago
603b5667b6
fix some non-gcc compiler warnings and signals in x11vnc
18 years ago
4b8cc33e39
x11vnc: fix AIX build wrt h_errno.
18 years ago
94b092cd22
x11vnc: -8to24 more speedups; tunables for very slow machines.
18 years ago
d0ef1285b8
x11vnc: -8to24 speedups and improvements.
18 years ago
1967913e95
x11vnc: -8to24 opts, use XGetSubImage. fix -threads deadlocks and -rawfb crash
19 years ago
17e6b6a2bf
x11vnc: -8to24 now works on default depth 8 displays.
19 years ago
e38c3c224b
x11vnc: more tweaks to -8to24 XGETIMAGE_8TO24
19 years ago
5993dd757e
x11vnc: add -8to24 option for some multi-depth displays.
19 years ago
60918e6664
configure.ac: add switches for most X extensions.
19 years ago
9b3163c00b
logMutex needs to be initialized too; in rfbDefaultLog.
19 years ago
57cf0cdab5
x11vnc: close fd > 2 in run_user_command(), -nocmds in crash_debug, fix 64bit bug for -solid.
19 years ago
0b7a0030ac
rfbProcessEvents() has to iterate also over clients with sock < 0 to close them
19 years ago
71f2ec7918
x11vnc: the big split.
19 years ago
def3012663
fix client non-jpeg/libz builds
19 years ago
e781eea698
rfbRegisterProtocolExtension extMutex was never initialized.
19 years ago
454c1fad65
x11vnc: enhance -passwdfile features, filetransfer on by default.
19 years ago
e673a125df
make compile again with pthreads; fix off-by-one error
19 years ago
1c26789eff
introduce -deferptrupdate (thanks Dave)
19 years ago
1b81e342cb
assorted fixes for MinGW32
19 years ago
3a8d4bdbe6
work around write() returning ENOENT on Solaris 2.7
19 years ago
065e2ebb7e
previous patch turned compile warning in a compile error; fix that ;-)
19 years ago
efbf1d7240
fix compile warnings
19 years ago
9e78be39cc
one more memory leak
19 years ago
61204490ce
plug memory leaks
19 years ago
6a7736f87a
translate keys based on unicode (much more reliable than sym)
19 years ago
54906d737d
x11vnc: add -loop option.
19 years ago
8eb18f6cd8
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.
19 years ago
de99644d2f
configure.ac: test ... == ... not allowed on all unix.
19 years ago
30c00d0b06
x11vnc: -filexfer, -slow_fb, -blackout noptr,...
19 years ago
94d7fc841e
update TODO
19 years ago
951ec26b7c
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.
19 years ago
2c177c866b
update ChangeLog for today
19 years ago
194a76df11
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.
19 years ago
11fc700c5d
add BackChannel extension example
19 years ago
5c1fdb47d3
fix warning
19 years ago
d15e35586b
kill BackChannel and CustomClientMessage: the new extension technique makes these hooks obsolete
19 years ago
60f1770e10
provide a list of the pseudo encodings understood by the extension
19 years ago
354d3c9a92
DEFINES -> AM_CFLAGS
19 years ago
808b6a0b23
do it right: it is not DEFINES, but AM_CFLAGS
19 years ago
8490de3ff0
add enablePseudoEncoding() to rfbProtocolExtension
19 years ago
1a20edd73f
more TODOs, and an update to the website
19 years ago
0a909fde7a
This monster commit contains support for TightVNC's file transfer protocol.
...
Thank you very much, Rohit!
19 years ago
93be927b1c
Introduce generic protocol extension method. Deprecate
...
the processCustomClientMessage() method.
19 years ago
94fcd86cc2
Security is global. This was a misguided attempt to evade a global list.
...
I eventually saw the light and went with Rohits original approach.
19 years ago
dscho
runge
rohit_99129