Less headends on json api

Less headends on json api

Postby cwchapma » Fri Mar 29, 2013 6:16 pm

There seem to be more headends listed on the old interface than the new for postal code k2j1t2. For example, Rogers is listed once for analog and once for digital in the old but only once in the new json. Shaw is listed in the old but not the new.

Again I'm wondering if I missed something.

Any ideas?

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

Re: Less headends on json api

Postby cwchapma » Fri Mar 29, 2013 7:12 pm

I'm still not sure why some like headends like Shaw don't show up but I see now that the Analog and digital channels for rogers are together in the lineup.

The format of the lineups is hard to decode though. I'm wondering if:

Code: Select all
{
   "name": "Rogers Cable Inc.",
   "location": "Ottawa",
   "deviceTypes": [
      "X",
      "Analog"
   ],
   "X": {
      "map": [...]
   },
   "Analog": {
      "map": [...]
   },
   ...


could change to:

Code: Select all
{
   "name": "Rogers Cable Inc.",
   "location": "Ottawa",
   "deviceTypes": [
      {deviceType: "X", map:[...]}
      {deviceType:"Analog", map:[...]}
   ],
   ...


In the first one, you got and object with an unknown number of members with unknown names, "X" and "Analog". It's far easier to decode if the all the member names (on the left side of the colons) are know before the request is made.

This would make it possible to load the data into static classes. Not only that, but it seems more concise.

Again let me know if I'm missing something.

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


Return to Developer

Who is online

Users browsing this forum: No registered users and 3 guests