summaryrefslogtreecommitdiffstats
path: root/rfb/rfb.h
Commit message (Collapse)AuthorAgeFilesLines
* mingw32 crosscompile fixes.Christian Beier2009-10-021-0/+1
| | | | | | | | | | | SOCKET is redefined in winsock2.h so #undef it where winsock2.h is included. The changes in rfbproto.c circumvent crosscompiler errors like 'S_IFMT' undeclared ...', the Makefile.am changes avoid building linux specific stuff for a win32 host target. Also added configure option to specify sdl-config. Signed-off-by: Christian Beier <dontmind@freeshell.org> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
* Thread safety for zrle, zlib, tight.runge2009-05-211-0/+11
| | | | Proposed tight security type fix for debian bug 517422.
* Move tightQualityLevel out of the JPEG specific partdscho2008-01-311-1/+2
| | | | | | | | The variable tightQualityLevel is used for ZYWRLE compression, too, so if libjpeg is not present, but libz is, we still need to have that struct member. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
* Make ZYWRLE thread-safe for multiple clientsdscho2008-01-301-0/+2
| | | | | | | | ZYWRLE used a static buffer, which does not work too well if you have more than one client in a threaded server. Instead, we have the data in the client structure now. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
* rfb.h: Do not misplace guardsdscho2007-04-061-1/+3
| | | | This buglet made it impossible to double include rfb.h from C++.
* Permit auth.c to test major versionsteven_carr2006-05-161-0/+1
|
* Support sending TextChat messages back to the clientsteven_carr2006-05-151-0/+2
|
* Default to RFB 3.8, add command line option to specify the RFB version.steven_carr2006-05-151-0/+3
|
* The great UltraVNC Compatibility Commitsteven_carr2006-05-151-16/+95
|
* Server Capability Encodingssteven_carr2006-05-041-0/+7
| | | | | | | rfbEncodingSupportedEncodings - What encodings are supported? rfbEncodingSupportedMessages - What message types are supported? rfbEncodingServerIdentity - What is the servers version string? ie: "x11vnc: 0.8.1 lastmod: 2006-04-25 (LibVNCServer 0.9pre)"
* Client Independent Server Side Scaling is now supportedsteven_carr2006-05-031-0/+10
| | | | Both PalmVNC and UltraVNC SetScale messages are supported
* Ultra Encoding added. Tested against UltraVNC V1.01steven_carr2006-05-021-0/+17
|
* add KeyboardLedState extensiondscho2006-03-281-1/+8
|
* add handleEventsEagerly flag (Thanks, Donald)dscho2006-02-281-1/+4
|
* Added method to get extension specific client datarohit_991292006-02-241-1/+1
|
* Added method to get extension specific client datarohit_991292006-02-241-0/+1
|
* add functions to unregister extensions/security typesdscho2006-02-221-0/+3
|
* introduce -deferptrupdate (thanks Dave)dscho2005-12-191-0/+7
|
* The PseudoEncoding extension code was getting silly:dscho2005-10-071-1/+1
| | | | | | | | | | | | | | | | | | | | 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.
* kill BackChannel and CustomClientMessage: the new extension technique makes ↵dscho2005-10-061-13/+0
| | | | these hooks obsolete
* provide a list of the pseudo encodings understood by the extensiondscho2005-10-061-1/+5
|
* add enablePseudoEncoding() to rfbProtocolExtensiondscho2005-10-031-0/+3
|
* This monster commit contains support for TightVNC's file transfer protocol.dscho2005-09-281-5/+15
| | | | Thank you very much, Rohit!
* Introduce generic protocol extension method. Deprecatedscho2005-09-271-1/+30
| | | | the processCustomClientMessage() method.
* Security is global. This was a misguided attempt to evade a global list.dscho2005-09-271-4/+1
| | | | I eventually saw the light and went with Rohit´s original approach.
* support VNC protocol version 3.7dscho2005-09-261-1/+21
|
* fix compilation for systems without socklen_tdscho2005-05-181-4/+0
|
* hide strict ansi stuff if not explicitely turned on; actually use the ↵dscho2005-05-181-0/+4
| | | | socklen_t test from configure.ac
* ANSIfy, fix some warnings from Linus' sparsedscho2005-05-151-1/+4
|
* socketInitDone -> socketStatedscho2005-05-071-1/+11
|
* add '-listen ipaddr' optionrunge2005-03-051-2/+4
|
* implemented Floyd-Steinberg dither in order to rfbMakeMaskFromAlphaSourcedscho2005-01-211-0/+1
|
* pointerClient was still static.dscho2005-01-181-48/+10
| | | | | | | | | | | | | | | | | | | | | | do not make requestedRegion empty without reason. the cursor handling for clients which don't handle CursorShape updates was completely broken. It originally was very complicated for performance reasons, however, in most cases it made performance even worse, because at idle times there was way too much checking going on, and furthermore, sometimes unnecessary updates were inevitable. The code now is much more elegant: the ClientRec structure knows exactly where it last painted the cursor, and the ScreenInfo structure knows where the cursor shall be. As a consequence there is no more rfbDrawCursor()/rfbUndrawCursor(), no more dontSendFramebufferUpdate, and no more isCursorDrawn. It is now possible to have clients which understand CursorShape updates and clients which don't at the same time. rfbSetCursor no longer has the option freeOld; this is obsolete, as the cursor structure knows what to free and what not.
* add cursor alphablending to rfb.h cursor.c, x11vnc -alphablend -snapfb etc..runge2005-01-161-0/+2
|
* return value of rfbProcessEvents tells if an update was pendingdscho2005-01-141-2/+3
|
* add hook to allow for custom client messagesdscho2005-01-031-0/+5
|
* fix compilation on non MinGW32...dscho2004-12-011-0/+4
|
* support MinGW32!dscho2004-12-011-1/+5
|
* global structures/functions should have "rfb", "sra" or "zrle" as prefix,dscho2004-08-301-59/+58
| | | | while structure members should not
* fix cursor trails (when not using cursor encoding and moving the cursor,dscho2004-06-071-1/+1
| | | | the redrawn part of the screen didn't get updated, and so left cursor trails).
* add "-progressive height" option to make SendFramebufferUpdate "preemptive"dscho2004-01-211-0/+9
|
* ignore SIGPIPE by default; it is handled via EPIPEdscho2004-01-211-0/+1
|
* ZRLE no longer uses C++, but Cdscho2003-09-081-4/+4
|
* rfbErr introduceddscho2003-08-061-1/+1
|
* rfbLog can be overridden; EINTR on read/write means just try againdscho2003-07-311-1/+2
|
* add rfbclient.h to distribution; avoid C++ style commentsdscho2003-07-301-2/+1
|
* API change: Bool, KeySym, Pixel get prefix "rfb"; constants in rfbconfig.h ↵dscho2003-07-301-86/+86
| | | | get prefix "LIBVNCSERVER_"
* further valgrinding showed leaked mallocsdscho2003-07-291-0/+2
|
* fixed maxRectsPerUpdate with Tight encoding bug; some autoconfing; stderr ↵dscho2003-07-281-8/+8
| | | | should not be used in a library (use rfbLog instead)
* synced with TightVNC and RealVNCdscho2003-07-281-0/+7
|
generated by cgit v1.2.1 (git 2.18.0) at 2024-12-23 19:49:23 +0000