Lineups can be deleted from the server side; handle the situation. May want to backfit to 20131021?
Robert said:
I wasn't properly handling deleted lineups before; I only discovered
it while stepping through code chasing down another issue.
I've already added 2106 to the 20140530 API and would like to backport
it to 20131021; there are some users that have lineups that have been
deleted server-side who have been still pulling data, but they need to
know that the lineup that they're using is no longer valid.
So, the lifecycle of a lineup will be:
Active -> Deleted -> 10 days -> Purged.
Once a lineup is in "D" status the user will need to take action. I
can set a message for that user in the status response, but I don't
know if users pay attention to those.
Thoughts?
So will lineups have this status flag as part of their metadata when pulled?
I'll make it available in the metadata for programmatic responses and
will generate a user status message. At least on the MythTV side, the
issue is that it only supports a single message in the notification
field, so if there's more than one message it may just have to be a
pointer that says, "Go look at the messages in
/tmp/schedulesdirect_messages
Log in to post a comment.
