| |||||||||||||
Zeuthen: Writing a C library, part 1Zeuthen: Writing a C library, part 1Posted Jul 1, 2011 9:46 UTC (Fri) by dgm (subscriber, #49227)In reply to: Zeuthen: Writing a C library, part 1 by nix Parent article: Zeuthen: Writing a C library, part 1
I believe that what really paranoid programs have to do is keep critical state in non-volatile memory (a disk, a remote machine, etc), and do everything possible to ensure that it's always consistent. That way it doesn't matter if the program goes away because of a programming error, a kill signal or the power going down in the middle of a system call.
(Log in to post comments)
Zeuthen: Writing a C library, part 1 Posted Jul 1, 2011 13:40 UTC (Fri) by nix (subscriber, #2304) [Link]
Yes, probably. And then we can get into fsync() flamewars instead! Isn't POSIX fun?
Zeuthen: Writing a C library, part 1 Posted Jul 3, 2011 23:09 UTC (Sun) by dgm (subscriber, #49227) [Link]
We can probably shortcircuit the flamewar by using a relational database. Oh, noes! PostgreSQL vs. MySQL anyone? ;-)
Zeuthen: Writing a C library, part 1 Posted Jul 3, 2011 23:40 UTC (Sun) by nix (subscriber, #2304) [Link]
And then we can write a nice high-performance FUSE filesystem on top of the relational database! And then we can run MySQL on top of that! (And then we can run the FUSE filesystem atop that, and run a virtual machine inside that filesystem. And then we have a nice room heater.)
|
|||||||||||||