On Wed, 2005-09-14 at 08:30 -0500, Joe Lapp wrote: > > Just a note: At least Unix systems (but I'm pretty sure the same is true > > for Windows) do cache frequently accessed filesystem data in memory... > > so you haven't that much disk activity for read only accesses. In fact > > it would be possible to install DokuWiki on a RAM disk... > > You're right. I wasn't being entirely fair. It's a difference in tailoring > for the task. What are disk blocks, 1K or 4K in size? Sometimes you have to > cache two blocks if the little bit of data spans a block boundary. And you > still have to cache one block per file the data might be found in. So even > though technically the file system does cache, the caching is poorly > optimized for piecemeal data retrieval. > > But yes, I realize that you're focused on getting a release out and I'm > distracting you and everyone else from the task. I thought I'd seed the idea > in people's minds while it was in my mind, because the main take-away is, > let's abstract functionality behind interchangeable interfaces as we design. > i agree, all functions for accessing the data used by dokuwiki should be kept away in a backend, so that it would be easy to change parts to store it however you want.. > ~joe -- DokuWiki mailing list - more info at http://wiki.splitbrain.org/wiki:mailinglist