Posted by Robert G Laurin on June 26, 2008 at 07:45:59:
A little while ago I brought up the little concern I have about Comet file system Crashing & Burning when a keyed file hits the 4GB wall.
If my memory serves me well, Jim had argued that the file system using a 32bit lseek couldn't move the pointer beyond the 4GB limitation and that it was part of the old file system written long time ago.
We also know that Comet's internal file pointers use 3 double-words and therefore can address much more data than the 4GB limitation. So no file conversion is required.
Some sort of suggestion that it would be part of Comet32 was made, but then I just wonder... Isn't it CFAM that handles files? So why do we need Comet32 if the file system is now totally outside the original code?
CFAM was re-written using new code and has been maintained up-to-date, so shouldn't CFAM be able to handle 4GB+ files?
I am bringing this up again, because my larger customer is about to crash and burn with a Customer Master that will soon hit 4GB (somewhere around Oct-Nov this year). They regularly hit the 4GB wall with log files but that we can manage.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.