Issue #3: Id's in json for lineups and schedules?

Post Reply
cwchapma
Posts: 42
Joined: Fri Mar 29, 2013 8:32 am

Issue #3: Id's in json for lineups and schedules?

Post by cwchapma » Sat Apr 06, 2013 5:12 pm

https://github.com/SchedulesDirect/JSON ... e/issues/3

Is it possible to have the headend id included in lineups instead of just the name and location and then having to decode the id from the filename?

Ideally, the all the data is in the JSON and the zip and files are just a generic way transferring the JSON so each request doesn't have it's own special code. I would like to simply loop through the files in the zip and convert the JSON in each file to an object without having to parse data from the file's name.

I guess this means the "get schedules", instead of returning just an array of program data:

[ { program1 }, {program2}, ...]

would return:

{"station":"xxxxx", "programs":[ { program1 }, {program2}, ...]}

Does that make sense?

The same idea should apply programs as well. Not sure there are others.

Thanks,
Clint
Last edited by cwchapma on Mon May 06, 2013 7:25 pm, edited 1 time in total.

rkulagow
SD Staff
Posts: 915
Joined: Tue Aug 14, 2007 3:15 pm

Re: Id's in json instead of filename for lineups and schedul

Post by rkulagow » Mon Apr 15, 2013 9:39 am

I'm not sure if this would break existing clients, but at least the get->schedule seems like it's doable without killing the server. However, at this point I just want to complete bugfixes for 20130331, so lets address the feature requests in API 20130425.

cwchapma
Posts: 42
Joined: Fri Mar 29, 2013 8:32 am

Re: Id's in json instead of filename for lineups and schedul

Post by cwchapma » Mon Apr 15, 2013 10:27 am

Sure. I'll wait for that update.

Thanks,
Clint

Post Reply