diff options
| author | Warren Dukes <warren.dukes@gmail.com> | 2004-04-07 11:54:22 +0000 |
|---|---|---|
| committer | Warren Dukes <warren.dukes@gmail.com> | 2004-04-07 11:54:22 +0000 |
| commit | 61cffd0e75176bc27b714921fd9c5df804f6c634 (patch) | |
| tree | 6fcc3c02e3b8c9d2a124f5849e7bc3045df7b886 | |
| parent | 4537b1e9ec3064c1c8a18dd0c433bfafb04c0d26 (diff) | |
| download | mpd-61cffd0e75176bc27b714921fd9c5df804f6c634.tar.gz mpd-61cffd0e75176bc27b714921fd9c5df804f6c634.tar.xz mpd-61cffd0e75176bc27b714921fd9c5df804f6c634.zip | |
a journaled db?
git-svn-id: https://svn.musicpd.org/mpd/trunk@627 09075e82-0dd4-0310-85a5-a0d7c8717e4f
| -rw-r--r-- | TODO | 8 |
1 files changed, 6 insertions, 2 deletions
@@ -4,7 +4,11 @@ c) fork on update d) have a special case where if a update is in a command list, it only forks at the beginning of the list, and writes at the end of the command list e) add an element to status stating the "update state" - f) only pass back changed info to parent - g) only pass mtimes and paths to child + f) before a fork, the parent gets the position at the end of the db file + g) update child will dump changes to end of db file, this can effectively be a journal + h) parent reads changes at end of db file when update child is done + i) when mpd exits, dump the current db to the file, this will erase an journal entries + j) if there are journal entries on mpd start up, read the changes, then dump the entired db back to disk, and elimanate journal entries + 2) rewrite interface stuff, specifically command list handling etc so its less of a hack and deals with the above update stuff better |