Lets bundle forces

Ian Simcock ian "at" jobmax.com.au
Wed, 16 Jan 2002 02:17:21 +0000


Hi Guys.

I like the idea of everything being done as external libraries. That make
upgrading a bit easier as new libraries can be created and installed without
recompiling the client or server.

One of the ideas I had on my "If I ever have way too much time on my hands
and want to rewrite VNC" was that once everything was in libraries then if
the client and server identify their processor and operating system to each
other then they can hand out new and upgraded libraries. My thought here was
then you could do things like install the server on 500+ machines around
your company, configure then to never offer upgrades and to always accept
upgrades from the small range of IP addresses assigned to you support
people. Then, when the support people install a new encoder, compressor or
new sub app, like a remote printer, or file sharing, then that will
automatically be installed to the users machine the next time that they
connect. No more upgrading hundreds of machines!

Ian Simcock.



----- Original Message -----
From: "Michael Ossmann" <michael.ossmann "at" alttech.com>
To: <vnc-list "at" uk.research.att.com>
Sent: Wednesday, January 16, 2002 3:39 AM
Subject: Re: Lets bundle forces


> On Tue, Jan 15, 2002 at 01:03:54PM +0100, Rudi De Vos wrote:
> > Const's TightVNC  is essential, but the tight version is not a good
> > starting point.
>
> Why is that?  Because it is not as modularized as we would like?  Is
> there a better starting point, or do you think it would be best to build
> a new code base from the ground up?  I'd certainly like to see as much
> reuse as possible.
>
> > Encoders should be plug-ins (client and server site).    The same for
> > authentication and other stuff.
>
> Agreed.
>
> > Take a standard VNC (ex AT&T) and modified it to use plug-ins.  So
> > everybody can work on the parts and platforms they know the best,
> > encoders authentication, ssh,scaling....
>
> I'd like to see the protocol support provided by LibVNCServer
> [http://libvncserver.sourceforge.net] or something like it.  Having a
> library that other projects can use would be a good thing.
>
> > My focus is speeding up winvnc-server
>
> Excellent.  My experience is more on the Unix side, but my focus is to
> do what I can to help the emergence of a de facto standard VNC
> distribution and ease the fragmentation woes.
>
> --
> Mike Ossmann, Tarantella/UNIX Engineer/Instructor
> Alternative Technology, Inc.  http://www.alttech.com/
> ---------------------------------------------------------------------
> To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
> 'unsubscribe vnc-list' in the message BODY
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------