That said, the linux filesystem has been pretty well tested over the years. +
That said, the unix filesystem is pretty good at not losing your data -- + a point that was famously made by startup guru paul graham, + who created the web app that would eventually become yahoo stores by just storing all application state in files. hunk ./templates/maciddatasafety.st 70 - And even though I am a linux fanboy I have to admit, you're probably - pretty safe keeping your data on the windows filesystem too. +
If you use windows or mac, you probably believe these filesystem are pretty reliable too. hunk ./templates/maciddatasafety.st 72 -
(This point was famously made by startup guru paul graham, who created the web app - that would eventually become yahoo stores by just storing all application state in files.) - - hunk ./templates/maciddatasafety.st 84 -
My understanding is that macid serialization works by writing state change event data - one file at a time, and that by "replaying" the information here - in the order specified by the file names, you can recreate the state up to the time of the last write. +
Macid serialization works by writing state change event data + one file at a time. At server startup, HAppS "replays" all the information here + in the order specified by the file names. hunk ./templates/toc.st 10 + , ("","get and post data") hunk ./templates/toc.st 12 - , ("/tutorial/macid-data-safety","macid data safety and backups") + , ("/tutorial/macid-data-safety","using macid safely") hunk ./templates/toc.st 14 - , ("","form post data") - , ("","querystring get data") - , ("","macid data")