As Alexey stated, it could be good to put a clear list of new features required
for a next generation CVS network code.
Here we use CVS every day (yes, even during suny sundays ;) and we are really
happy with it!
But (there is always a 'but') we have some concerns regarding network.
We need something to improve the transmission of (big) files.
I don't know the intrinsics of CVS but it would be really good if:
- files are transmitted by incremental diffs (like rsync)
- files are transmitted compressed on a per file basis (to avoid trying to
compress kinds of files like jpegs)
- the compression scheme may even extend to repository storage? (but this may be
another topic)
- keep in mind that there are WAN with BIG latency (here >300ms) and round-trips
may kill us. (this is why we choose CVS instead of clearcase... clearcase on a
laging WAN is really a disaster)
I know these topics have already been discussed... but there is really something
to do here.
just my 2c...
Olivier
