oysteikt/mpd
0
0
Fork 0
Code Issues Pull Requests Releases Activity

a journaled db?

Browse Source 
git-svn-id: https://svn.musicpd.org/mpd/trunk@627 09075e82-0dd4-0310-85a5-a0d7c8717e4f
This commit is contained in:
Warren Dukes
2004-04-07 11:54:22 +00:00
parent 4537b1e9ec
commit 61cffd0e75
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
TODO
View File

@@ -4,7 +4,11 @@
c) fork on update 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 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" e) add an element to status stating the "update state"
f) only pass back changed info to parent f) before a fork, the parent gets the position at the end of the db file
g) only pass mtimes and paths to child 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 2) rewrite interface stuff, specifically command list handling etc so its less of a hack and deals with the above update stuff better