Channel Updates
In the case we have a channel update, which of course has to go through Roku approval, and is released once approved, what if that update involves a schema change in our backend database web services?...
Forum Discussion
Yeah, Since the Roku data is pretty static (other than user data), I have my web services do data dumps onto a single serialized agrregate data file every 15 minutes, along with associated serialized detail files on movies (cast, etc) that the Roku reads via simple http and deserializes. The dumps are strored in a directory named by schema version (like 20150503), and the Roku (and other devices) grab the schema level they are looking for. Once the web services move on to a new schema, the old dumps just stay, and any unupdated devices pull they revision they want. Is a simple kludge and what I mean by 'forms of versioning', but it could be better, ideally when the Roku calls the web service stat function which gives current schema number (a call that is fixed in its format - schema, server datetime, a session hash key, etc.), I could force a Roku channel update even if its midday, but I don't think such an option exists. Am just looking for any thoughts of better ways or ideas, and as always I greatly appreciate your input.
