An example of projects that use the current TightVNC codec are Chicken of the VNC and OSXVNC, Mac versions of the VNC server and client. Given the high degree of specialization required to build Mac applications, these types of codes are not ones we would want to merge into our project.
There are other types of specialized codes, like x11vnc, that use the TightVNC codec with few modifications. I think it is unrealistic to say that people can just use the protocol. There is a lot of complexity to the vnc-tight protocol, and even more that we plan to add. It's not very hard to take the C++ class and re-use it, but it's much harder to try and figure out what the class is doing. My personal opinion of GPL v3 is that it's all smoke and no substance. I think that there is a lot of FUD being generated in the OSS community around GPL v2 in an attempt to get people to upgrade, but the reality is that if GPL v2 were really that dangerous, there would have been a lot more exploits of it. IMHO, as soon as major projects such as the Linux kernel move to GPL v3, that would be an appropriate time to look at it. Pierre Ossman wrote: > I think we should primarily strive for good, well documented protocols > more than having people copying code. As part of that we should minimise > the use of tight's custom extension system and work more in line with > the regular RFB protocol. > > And in reality, how many projects can actually take our code? The code > isn't exactly general, so I would assume it's primarily any other > direct forks of TightVNC that could use it. And IMO we should work to > merge any such forks into TigerVNC. > > Rgds > ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
