What to do when a socket is writeable should be handled in the
RFB core code as there may be other events we want to fire off
when this happens.

We have lots of code that deals with Windows versions that we no
longer support anyway. Clean out all of this old cruft.

We don't have any meaningful code for the mirror driver, so
remove the confusing stub and interface for it.

The identifier is used to compute the registry path, and should
ideally be kept short and without spaces.

The argument named "desc" was not actually the description, but
rather the short "display name". Add handling for the actual
description to reduce confusion.

It is easier to control object life time and avoid magical socket
duplication by having a single TcpListener object to pass around.
We have to be more careful about deleting the object though.

The IPv6 additions deprecated support for netmasks in the access
control lists. Unfortunately some documentation was not updated
to reflect this fact.

Avoids conflicts with the original RealVNC implementation, or any
other forks of that code.

It is needed by WinVNC, but got removed in 892d10a70. Also fix
a couple of issues:

 - Use getnameinfo() in order to be compatible with Windows XP
 - Make it static since it doesn't use a specific socket
 - Respect UseIPv4 and UseIPv6
 - Flags for getaddrinfo() that match binding code
 - Dummy service value for Windows compatibility

Solve it by casting to the larger of the two, i.e. 64-bit.

Either by casting, or switching to a more appropriate type
for the variable.

Clearly separates the read API from the write API
and also from actual implementation.

It was confusing and not properly used everywhere.
Callers should use the stride they get when they get
the buffer pointer.

Gets rid of a loooot of code and complexity.

Colour map clients are still supported through an
automatically generated map, but we lose the ability to
develop a client or server that uses colour maps
internally.

It's either not used, or no longer relevant.

There were also reports of them being broken last time we still
made use of them.

git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@5159 3789f03b-4d11-0410-bbf8-ca57d06f2519

Patch by Jochen Tucht, fixes bug 135.



git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@5158 3789f03b-4d11-0410-bbf8-ca57d06f2519

git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@5157 3789f03b-4d11-0410-bbf8-ca57d06f2519

git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@5122 3789f03b-4d11-0410-bbf8-ca57d06f2519

before windows.h for correct winsock behaviour. mingw-w64 also enforces
this order, so to avoid compile errors we must include windows.h late in
all files.


git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4906 3789f03b-4d11-0410-bbf8-ca57d06f2519

git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4905 3789f03b-4d11-0410-bbf8-ca57d06f2519

only works with MSVC.


git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4897 3789f03b-4d11-0410-bbf8-ca57d06f2519

git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4896 3789f03b-4d11-0410-bbf8-ca57d06f2519