At 11:21 AM 02-01-01 +0000, you wrote:

>The other problem with FreeVCS is that it is Delphi only!

You can use the FreeVCS stand-alone client - the IDE version is
optional. You can store any text file.

I have a FreeVCS server running over a 5.6 database for Project JEDI. It
works fine but of course it uses the BDE.

I discussed with Thomas Hensle about building an IBO server program - he's
keen on the idea. It's Open Source, of course, which means the code has to
go back. I started to spec it up and it gave me a headache. The problem
is that this is an ULTRA FAT CLIENT application. It was built originally
over DBISAM so it uses exactly NO server side processing. Even the
stand-alone client is about 4 Mb. There is sooooo much in that client that
should be moved over to the server - both the FreeVCS server and
(particularly) the database. The server program is only about 750Kb and
really only looks after connections.

Thomas is now supporting MSSQL and Oracle as well as IB and DBISAM. My
feeling is, there should be a fork in the code so that a properly optimised
server program can be done for the C/S databases. Starting with InterBase,
of course.

Someone made an IBX version for IB 6 but it doesn't seem to work properly
yet. I saw it at first beta release time and it didn't seem like a radical
revamp of the architecture - rather, just a straight conversion of the
existing server program.

>I have not seen this in any of the Version Control systems I have
>looked at, but then I keep hitting 'Delphi Only' !

Any version control system will accept plain text files. 'Delphi Only' is
only a limitation if the VCS won't work outside the IDE. PVCS, for
example, is written completely in Java but half the world uses it. Version
control systems aren't mean to store binaries; some will, but of course
you can't do compares on the versions so it's pretty meaningless.

H.

All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
_______________________________________________________