![]() ![]() This depends on what the renderer supports and other factors. There's another thing that happens as well, and that is that UMS "calculates" in what form the media can be presented to the renderer. That said, entering a folder should be fairly quick if the cache has been populated, as the files themselves doesn't need to be analyzed. The advantage is that changes are reflected (to some extent, but there are other issues that means that's still not always the case), the disadvantage is first and foremost the speed. Either way, the folder contents will be enumerated each time. If it has, the information is gotten from the cache, if not it is parsed and stored in the cache. UMS does this differently, it actually checks the content of a folder each time you enter it, and then looks in the cache if the information for each file has been cached. ![]() The simple scenario probably employed by most is that folders are scanned, the content indexed in a database, and then all browse requests from renderers are fetched exclusively from the database. But, it doesn't do it "completely" - which I suspect many other servers (like Serviio) do. ![]() UMS does scan the folders in the background, and does cache the results so that the content is displayed faster. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |