suggestions to customize browsing

[simoncn]

(06-09-2012 08:35)winxi Wrote:  

(05-09-2012 16:07)admin Wrote:  The difficulty will be agreeing what algorithms should be used to decide the contents of these lists.

I guess that the most straightforward way would be to mark an audiofile as added if it has changed in any way, i.e. if it gets updated in the database during a server restart. All other possibilities (e.g. ignoring a changed filename or retagged files) would involve computing some kind of fingerprint of the audio data at the expense of performance. During server restart, how do you now determine if a file has changed?

What are the different possibilities to decide if a file has been played?

It's not too hard to detect that a file has changed. When MinimServer starts, it looks to see if the file's timestamp or size has changed since it was last scanned.

What I meant was that it might be hard to agree on the meaning of "recently". This could be based on activity within a certain time period (such as the last month), or based on a fixed number of the last items to be added or played (such as the last 200 items), or perhaps some combination of these.

For "recently played", the only way MinimServer could detect this is by looking at HTTP GET requests for the audio data. This should produce fairly accurate results.