Skip to content

Feature Request: Include IDs in JSON instead of having to parse from filenames in zip #3

@cwchapma

Description

@cwchapma

For example, when getting lineups for a headend, the headend id is in the filename '0005410.json.txt':

Request:  {"randhash":"xxxx","request":["0005410","PC:K2J1T2"],"object":"lineups","action":"get","api":20130502}
Response: {"response":"OK","code":200,"serverID":"AWS-micro.1","message":"file available at URL.","filename":"2013-05-03T21:13:19Z.headends.json.zip","URL":"https:\/\/s3.amazonaws.com\/schedulesdirect\/lineup\/40a1deac1748cd6f3c9b6d04773e927b.zip","datetime":"2013-05-03T21:13:19Z"}

0005410.json.txt: {"name":"Rogers Cable Inc.","location":"Ottawa","deviceTypes":["X","Analog"],"X":{"map":[{"stationID":14786,"channel":"001"}, ...

This is far simpler to parse if the headend id is included in the json:

0005410.json.txt: {"headend":"0005410","name":"Rogers Cable Inc.","location":"Ottawa","deviceTypes":["X","Analog"],"X":{"map":[{"stationID":14786,"channel":"001"}, ...

I think the name and location are just repeats of what's in the headend data so they could be removed if the headend id is included.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions