Michael, Folks:

I hate chewing up bandwidth saying "I agree" 
but that was awfully well stated. I do hope 
AT&T does, in fact, bring out an update and 
make some modest improvements to VNC so that, 
as you put it, they put their blessing on 
an updated version. In the grand scheme of 
things, the expense would be small to AT&T 
and a lot of us IT folk will remember such 
when making various and sundry decisions.

We have been using VNC for about three years 
now and consider it among our most valuable 
networking tool.

Alexander 
In Toronto


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Michael F. March
Sent: Monday, April 01, 2002 9:23 AM
To: [EMAIL PROTECTED]
Subject: Re: AT&T


All these forks of VNC development have been great and they
show that VNC development is by no means stagnant. The issue
I think is on most people's mind (or mine at least) is that
we all look to AT&T as the 'pure' source of VNC and from time
to time we would like AT&T to take the "best of the best"
features of all the features that have been brewing out
there and incorporate them into AT&T's own version. I don't
think people want AT&T to go nutz and put in every feature
that comes down the pike but things like Tight encoding which
I think everyone agrees should be core functionality at some
point should be blessed by AT&T by putting it into a future
release.

Having the AT&T version somewhat current will insure that more
people will contribute to VNC. If some organization wants
to extent VNC now, they have to pick from all these non-official
forks to base their extended functionality on. Have the AT&T
branch less stale makes this less of an issue. My fear is that
some people might be holding back work on VNC because they
are waiting for AT&T to catch up on some functionality that
they feel is missing.

Another issue... The longer AT&T waits to put out another
version of VNC, the harder it will be for the other forks
to 'sync' to the AT&T branch if they find that is one
of their goals.

[snip]
---------------------------------------------------------------------
To unsubscribe, mail [EMAIL PROTECTED] with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------

Reply via email to