Sat Nov 19, 2011 9:02 am
Separate expiration and update times for online media
Thank's for a fantastic and working media server!
I would like to have separate expiration and update times for online media. With update time I mean the intervall between rescans of the feed. With expiration I mean the time a specific item should stay in the database. Today the database is simply replaced at each rescan - i.e. update = expiration.
The reason is that the rss-feed on e.g. SVTPlay is meerely an anouncement of new media than a list of existing media. Separating the two times would make it possible to have a repository of recently (the word "recently" defined by expiration) announced media rather than just the media currently announced. Personaly, I would probably scan each day but set the expiration time to at least a week or more.
A potential problem is that the repository would also contain some outdated items with obsolete links but I think it would be OK as a start. I'm not an expert on rss, but it seems like SVTPlay is using a proprietary tag stating the actual expiration time per item. Interpreting such tags would be the ultimate way of handling expiration but would require some code on a plug-in level since the tags seems to be proprietary.
Another potential problem is the precise method to decide if a rescanned item differs from a previosly scanned item. This criteria is crusial to avoid duplicates if the change in an item from last rescan is irrelevant. I.e from a mathematical perspective an equality relation of appropriate strength has to be defined.
Pen
I would like to have separate expiration and update times for online media. With update time I mean the intervall between rescans of the feed. With expiration I mean the time a specific item should stay in the database. Today the database is simply replaced at each rescan - i.e. update = expiration.
The reason is that the rss-feed on e.g. SVTPlay is meerely an anouncement of new media than a list of existing media. Separating the two times would make it possible to have a repository of recently (the word "recently" defined by expiration) announced media rather than just the media currently announced. Personaly, I would probably scan each day but set the expiration time to at least a week or more.
A potential problem is that the repository would also contain some outdated items with obsolete links but I think it would be OK as a start. I'm not an expert on rss, but it seems like SVTPlay is using a proprietary tag stating the actual expiration time per item. Interpreting such tags would be the ultimate way of handling expiration but would require some code on a plug-in level since the tags seems to be proprietary.
Another potential problem is the precise method to decide if a rescanned item differs from a previosly scanned item. This criteria is crusial to avoid duplicates if the change in an item from last rescan is irrelevant. I.e from a mathematical perspective an equality relation of appropriate strength has to be defined.
Pen