Common spec/interface for file metadata

[nf2]

Jamie McCracken wrote:

>
> The problem is then how do you take advantage of existing frameworks 
> under developemnt like Beagle, Kat and Tenor. They are the ones that 
> are producing the metadata in the first place and they each store it 
> in their own databases (Beagle uses lucene's DB, Kat Sqlite3, Tenor 
> Postgres and my own implementation of a metadata framework will use 
> the embedded mysql lib) so its kind of difficult to standardise it 
> in-process plus you also have a potentially huge dependency list which 
> no platform would accept in its core. Unfortunately I cant see any 
> other way round this but IPC.
>
>
To avoid the dependency problem a plugin model would be feasible 
(dlopen). But you won't be able to use those plugins in-process unless 
you have a common main loop 
(http://www.scheinwelt.at/~norbertf/common_main_loop/). It's a pity that 
nobody wants to fix this.

Norbert