Steve Baumgarten Wrote: > I kind of understand what's going on behind the scene. If you think > about it, what can SlimServer do when it descends into a directory? > > If it just spit back a raw directory listing, well, that's OK as far > as > it goes, but then none of the tracks would be "clickable". That is, it > could show you what's there, but it wouldn't understand what it was > showing you. I'm not sure I follow - what information does SlimServer need to know about the file to make it "clickable"? All it really needs is an extension to know if the file is a type that it can play. If you mean the detailed information that you see when you click the file, then the task of pulling the info from a single file should be trivial at the rate that a human being can browse and click them. The server might also need this info when it plays a track, but once again, this doesn't _have_ to come out of the database.
> If a raw directory listing is fine, as I think it should be done This > would be akin to my tiny perl script that runs super > fast but has no understanding of what it's listing. I think a raw listing is fine as well. Display only the directory and file names. Restricting files shown to music files makes sense when browsing using the remote and the Squeezebox screen. When browsing through the web interface it would make sense to be able to see all files. Graphics files should be clickable, so you can view cover art, booklet scans, etc. > The alternative is for SlimServer to do a lookup for each track it > encounters -- this way it can "understand" what it's showing you in a > directory listing. > > Mixed in with this is the idea of picking up newly added tracks and/or > directories, a limited "rescan", if you will. > > I guess what's confused me is that since all I have at the top level > of > my music folder is more folders (about 800 of them) and no loose > tracks, > I don't know what takes SlimServer so long. There's really nothing > going > on there for it to try to "understand", do lookups on in the database, > etc. So what's it doing as it's reading that top level directory? In this scenario I wonder if the the server is doing 800 database lookups to tell if it's seeing any new directories? Or should it only query the database when it encounters music tracks? -- JJZolx _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
