Well, they are different companies arent' they? There may be legal issues. Also, isn't RealVNC open source? That's probably TightVNC's starting point.
It would make life easier to have one version though. How does TightVNC compare to RealVNC when dialing up, say via a 56k line? Carl ----- Original Message ----- From: "Jerry McBride" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, January 18, 2003 1:11 PM Subject: Re: tight encoding in realvnc? > On Saturday 18 January 2003 12:10 pm, Shing-Fat Fred Ma wrote: > > > Hi, Fabian, > > > > I posted a while back to both forums asking > > about the likelihood of consolidating the two, > > RealVNC and TightVNC. It only makes sense, > > more so than to have RealVNC with tight > > encoding, and TightVNC as a separate project. > > There wasn't much response (none, actually) > > Who knows, maybe there are factors besides > > just technical feasibility. > > > > > Yeah... I think it's called, ego. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
