Maybe I am being a little over sensitive, but I want to make sure that my earlier comments were not taken in the wrong context since you used "Users" as in more than one. Since I was the only other user in the discussion I assume I was included in the problem users list.
I have supported VNC for about 6 years now mostly by answering questions on the mailing list but more recently with code and money. Most of my recent efforts have gone into TightVNC because for quite a while the official version was not updated and TightVNC filled an important gap in my needs. Now that RealVNC has launched, I am sure I will be using it along with TightVNC in my deployments. However, I still prefer TightVNC for low bandwidth. I find that the Tight encoding with JPEG compression is the best balance when connecting two machines over the Internet with a T1 line. ZRLE might be a good encoding and I have not benchmarked it against straight Tight encoding, but the TightVNC cursor handling makes the argument academic since this feature greatly increases feel and reduces bandwidth requirements. The Keyboard handling fixes alone that were recently added to RealVNC is a "Major" acomplishment and I would have probably switched all my deployments to RealVNC just for this if TightVNC had not included it in the new 1.2.7 release. For this I thank everyone involved in RealVNC development. Greg Breland > Following a post to this list regarding a new project based on VNC, there seems to > have developed a minor flame war, so perhaps I should clarify the situation: > > Apologies to the majority of this list for the tone of this mail, but I'm getting > a little annoyed by abuse of this list by some users. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
