Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Chuck, > > The current CVSNT 2.5.04 server has two diff types available: > > * one 'optimised' for text files > > * one 'optimised' for binary files (-kB) > > > > Storing each change as a complete 'blob' on the server is > > not a feature > > currently supproted by CVSNT. > > > > > This only applies to 2.5.4, correct? I didn't realize you had > deprecated -kb. The -kb is NOT deprecated and is the one that is 'optimised' for text files. This still stores binary files as diffs in the RCS file, just not diffs that are optimal for binary files. > Certainly there are a lot of legacy files stored on > servers that used the blob approach. CVS and CVSNT have NEVER EVER supported storing the entire revision. The rumour that -kb stores entire revisions is a myth (an often repeated myth is still a myth). > his problem. And even with binary differencing (-kB), you will > eventually exceed the server's memory capability, at least > with 2.5.3. > I haven't tried 2.5.4 yet. This has never been true. It is another myth. CVSNT has no memory limits beyond the limits of the C Runtime library and the underlying operating system. MS Windows C Runtime has a well known bug that can make it appear that applications linked to it cannot reallocate memory over 500Mb (and is often seen with CVSNT). If you use CVSNT on a platform without these limitations (eg: HPUX 11i) then CVSNT works OK. The commercial edition of CVSNT: CVS Suite includes some 'workarounds' to to work with larger files on MS Windows but the effectiveness of these varies on the situation. Regards, Arthur