Hi, There is no progress on the mediadb, so i'm proposing something again.
Had a disussiuon with Tack on IRC a while ago. He really wants scalebility (>100 000 files),and after some thought i do agree. The media he's working on for MeBox is a side project with lots of goals, no way of knowing when it's finished. My New goals: *scalability far beyond 100 000 media files *use sqlite. Back to (attr, value) mapping , Like wander proposed. I'm willing to make a sqlite mediadb with that schema. Good points: *scales *sqlite *"easy" to replace fxd files. Bad points: *more code *lots of joins for complex stuff *some really dynamic stuff will not be implemented [ but i love to prove me wrong ;-) ] *some challenges in implementing smart-query's + album-tree. -various- A static sqlite schema would be a lot easier but: But you search images on ISO, mp3's on artist and Video's on director. -my plans- 1: freevo cache,fill sqlite db 2: replace mediadb timestamp-compare/re-index on entering directory 3/4: minimal search/smart playlists/albumtree Evaluate , is it good enough? 5: audio.logger 6: improve search/smart playlists/albumtree 7: other freevo processes could ask the main freevo-process data via mbus. background indexing could also report back via mbus. Martijn. ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel