On Tue, Dec 09, 2003 at 08:48:47PM +0100, Dirk Meyer wrote:
> 1. Create a file for each directory to store that data. This is more
> or less duplicate work since mmpython does that.
I think this would be necessary, simply because mmpython is a seperate
program now.
> 2. You the mmpython cache. This is bad, because a) a cache shouldn't
> contain data that isn't stored somewhere else. Removing the cache
> will destroy your meta infos.
A generalized storage interface would be nice. For example, you would
create a meta item for each media file.
myfile = util.MetaStore(file)
myfile.store('PLAYDATE',date)
myfile.increment('PLAYCOUNT')
As you can see, it's very simple. We store a item for the file, the
item could be a string, int, float or boolean. I don't think we would
need to worry about type safety, but the increment function would want
a number and it would be silly to have to pull out the old item, add
one and then write it in every source file so an increment method
would be good.
And then, we could support multiple datastores outside of the code. So
we could use flatfiles now, and then move to sqlite or CSV or mysql or
whatever someone cared to write for.
Aubin
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
