Reply to thread

Message

<blockquote data-quote="marmite" data-source="post: 194492" data-attributes="member: 48853">Yes, I agree, the scheduler should schedule, the kind of functionality I describe, should involve the scheduler, but not be coded within it.I pointed it out here, because it will involve the scheduler if only to query it and potentially cancel and so there should be some API to ask the right questions, but thinking about it more, you probably could handle this _completely_ independently already by interrogating the dB.I was hoping eventually, that the rules of the new scheduler, could define this behavior by default.IOW - a rule set defined for a series, a episode is missed for _whatever_ reason, the scheduler is aware that episode X#n has still not been recorded, and so if it re-aires it will record next time.BTW: This is how Tivo handles things - this behaviour, handles power cuts, priority conflicts, etc.If the client choosed to cancel an individual episode for whatever reason, I'd like the scheduler to do the smart stuff of rescheduling if possible. I guess the client _could_ check with the scheduler and warn if no repeats. But I'd prefer to keep it simple, with maximum logic in the scheduler itself.I do not know the code base at all and have never coded in c#, I fetched the sources last night and found the code that detects the scheduler/livetv conflict.. Just curious, what (if any) mechanisms are there for relaying messages to the client? Or is everything currently 'pulled' by the client?</blockquote>

[QUOTE="marmite, post: 194492, member: 48853"] Yes, I agree, the scheduler should schedule, the kind of functionality I describe, should involve the scheduler, but not be coded within it. I pointed it out here, because it will involve the scheduler if only to query it and potentially cancel and so there should be some API to ask the right questions, but thinking about it more, you probably could handle this _completely_ independently already by interrogating the dB. I was hoping eventually, that the rules of the new scheduler, could define this behavior by default. IOW - a rule set defined for a series, a episode is missed for _whatever_ reason, the scheduler is aware that episode X#n has still not been recorded, and so if it re-aires it will record next time. BTW: This is how Tivo handles things - this behaviour, handles power cuts, priority conflicts, etc. If the client choosed to cancel an individual episode for whatever reason, I'd like the scheduler to do the smart stuff of rescheduling if possible. I guess the client _could_ check with the scheduler and warn if no repeats. But I'd prefer to keep it simple, with maximum logic in the scheduler itself. I do not know the code base at all and have never coded in c#, I fetched the sources last night and found the code that detects the scheduler/livetv conflict.. Just curious, what (if any) mechanisms are there for relaying messages to the client? Or is everything currently 'pulled' by the client? [/QUOTE]

Verification