On 6/3/05, Jason Tackaberry <[EMAIL PROTECTED]> wrote: > On Fri, 2005-06-03 at 19:14 +0200, Martijn Voncken wrote: > > It makes some simple things more complex, but i do agree on scalability. > > Thinking about it. (and how to do the simple things) > > Yes, the things we do in the name of performance. :)
Yep, and i still want to keep the simple things simple ;) Finding the "right" compromise, I'll sleep over it. > INotify. I lost you there, googling.... Ok, "Inotify is a file system event-monitoring mechanism for kernel 2.6+" > But there's another use-case. Imagine indexing images on a CD and > storing into the mediadb. The CD later gets mounted under a different > path. So including the path in the files table is problematic there. > You could, I suppose, use a URI scheme for that which includes a hash of > the CD id and title or something. > cd://14758f1afd44c09b7992073ccf00b43d/path/to/foobar.jpg. But I think > using a dirid here is better design. The URI/md5/Hash scheme would still be needed to identify an inserted CD. But after identifying, renaming inside the mediadb would simplify things later on. Cheers, Martijn. ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
