Pathologically Eclectic Rubbish Lister | |
PerlMonks |
Re: Re: Re: Re: Re: writing to the top of a fileby jepri (Parson) |
on May 21, 2004 at 02:59 UTC ( [id://355163]=note: print w/replies, xml ) | Need Help?? |
using the file system as a DBMS for tracking thousands of itty-bitty chunks of information is a ridiculous misuse of file system resources So what are we supposed to use it for? Tracking icecream? The point of a filesystem is to store my data. If it can't do what I want, then I just need a better filesystem. When you create many thousands of one-line text files, you pay a severe penalty in OS and hardware I don't believe that the penalty is too bad. If you post figures, I'd like to have a look - sounds interesting. Not to mention that you'd need to complicate things a bit more to make sure file names don't collide -- this can get hairy when multiple threads or processes are abusing the file system this way. Multiple threads are abusing the filesystem by writing to it? What kind of computer are you using? Filesystems are there so that multiple processes can read and write files without stepping on each others toes. Seriously. What were you thinking when you wrote this? Do your store your files on reel-to-reel tape? POSIX provides the tmpfile() call, which guarantees a unique temporary file. Perl has its own tempfile module called File::Temp, which apparently uses the same call. There is no 'hairiness' at all. Demonstrating this lack of knowledge makes your other assertions look suspect.
In Section
Seekers of Perl Wisdom
|
|