API: Library Refresh
Posted: Sun Nov 17, 2013 12:21 pm
Hi zip,
I am working on customising the library refresh using my WinHelper tool. A couple of questions if I may:
Any concerns or issues you foresee would be greatly appreciated.
I am working on customising the library refresh using my WinHelper tool. A couple of questions if I may:
- If an app forces a library refresh using the configuration API (posts a /rest/action/forceLibraryRefresh) and then does so again before the first refresh is finished - what happens. Does it:
- Ignore the second request
- Start the refresh process from the beginning (terminate current refresh process and start again)
- Queue the second request and process it once the first refresh is finished
- If a refresh begins, and the scanForUpdates for a particular folder is subsequently changed (before the refresh is finished) does it affect the currently running refresh process? For example, if the scanForUpdates for folder C:\XXX is true, and then a /rest/action/forceLibraryRefresh is issued (starting the refresh process) and then very shortly after, the scanForUpdates for folder C:\XXX is set to false is C:\XXX included in the scan? (ie. does Serviio take a snapshot of the library scanForUpdates status at the beginning of the refresh process or does it check as needed throughout the process?).
Any concerns or issues you foresee would be greatly appreciated.