> Linux (the kernel anyway), has managed to maintain a common code base > for more than 10 years now.
Actually, that is misconception. There are multiple source trees for Linux (and the kernel). RedHat and Debain both have one, as well as other distros. Yes, they are closely liked, but still they are seperate. One business reason: Distro developer find a need and implements it, say a new hardware that *NEEDS* kernel support. Then sends the diff into Kernel Team for *future* inclusion. The Kernel Team can reject (meaning the distro developer supports it itself), includes it (so the distro is off the hook, so to speak), or uses the base idea and goes another way (so the distro developer is stuck to move to new method or support old method). This will get worst as RedHat and others - start to step up to multiple year support for a given version. > Why cann't the various folks building VNC > functionality, merge their efforts? More bugs will be fixed and more > features would be added in a shorter time frame by far, once the initial > merge were completed, and a public CVS repository created (source forge > comes to mind). One reason comes to mind... File transfer or NOT. For me not, there are others ways. Also there may be other functions makes one more or less better. What is nice is having a choice. It would be great that common API is kept, so a UltraViewer could use a RealServer. That is for the three+ teams to work out, so all can inter-work. jackb _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
