Developer Wishlish for new JSON API

Slugger
Posts: 77
Joined: Sun Sep 18, 2011 1:22 pm

Re: Developer Wishlish for new JSON API

Post by Slugger » Tue Feb 26, 2013 2:00 pm

I'm still having those problems I reported last night where I'm grabbing 7 headends, etc. Not sure if that problem will creep into production if you move things over?

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

Re: Developer Wishlish for new JSON API

Post by rkulagow » Tue Feb 26, 2013 6:06 pm

I'll check tonight to see why you're getting so many headends

hall5714
Posts: 20
Joined: Thu Feb 07, 2013 4:34 pm

Re: Developer Wishlish for new JSON API

Post by hall5714 » Thu Feb 28, 2013 5:22 pm

Sorry, this has been a bit of a hectic week, I'll get the python client updated this weekend with the changes.

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

Re: Developer Wishlish for new JSON API

Post by rkulagow » Thu Feb 28, 2013 5:45 pm

Slugger's issue has been resolved. I know that Slugger has user's that are actively using his client. If you're not sure if anyone is using yours yet, then I'd like to get the new API put on production sooner rather than later, and that way I've got cycles on the weekend to fix things. (Although I'm not expecting any)(famous last words)

Slugger, are you ready for API 20130224 to go onto production, or do you want to wait until the weekend?

Slugger
Posts: 77
Joined: Sun Sep 18, 2011 1:22 pm

Re: Developer Wishlish for new JSON API

Post by Slugger » Thu Feb 28, 2013 8:16 pm

I'm ready anytime. Just need to run fvt tests against production once it's up, assuming they pass, then I'm ready to go. Should be a 10 min job to release the update to the Sage repo.*

* That quote pulled directly from my infamous book, "Famous Last Words for Every Software Engineer". :P

Slugger
Posts: 77
Joined: Sun Sep 18, 2011 1:22 pm

Re: Developer Wishlish for new JSON API

Post by Slugger » Thu Feb 28, 2013 8:19 pm

Slugger wrote:I'm ready anytime. Just need to run fvt tests against production once it's up, assuming they pass, then I'm ready to go. Should be a 10 min job to release the update to the Sage repo.*

* That quote pulled directly from my infamous book, "Famous Last Words for Every Software Engineer". :P
The other favourite from that book: "Yeah, I just changed one line so no need to run regression tests or anything, just release it." I've got tonnes of these! ;)

hall5714
Posts: 20
Joined: Thu Feb 07, 2013 4:34 pm

Re: Developer Wishlish for new JSON API

Post by hall5714 » Fri Mar 01, 2013 11:45 am

Go ahead and release it. I only know of one person that suggested they may use it. It's not even a client technically, it's a library... it won't do anything except parse the data so developers can easily insert it into a database, file, zip it etc.

hall5714
Posts: 20
Joined: Thu Feb 07, 2013 4:34 pm

Re: Developer Wishlish for new JSON API

Post by hall5714 » Wed Mar 06, 2013 8:46 pm

{"response":"ERROR","code":401,"serverID":"AWS-web.1","message":"Wrong API version. Expected 20130107, received 20130224.","datetime":"2013-03-07T03:38:12Z"}

I'm assuming the base and/or request url has changed and I'm just not finding it?

Slugger
Posts: 77
Joined: Sun Sep 18, 2011 1:22 pm

Re: Developer Wishlish for new JSON API

Post by Slugger » Fri Mar 08, 2013 11:45 am

Are you testing against the test server? It's not the data2.schedulesdirect.org url. Not sure if Robert wants the test server url made public so I won't post it here. Email Robert for more details. Only the test server is running api 20130224 right now. The production server is still on api 0107

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

Re: Developer Wishlish for new JSON API

Post by rkulagow » Sun Mar 10, 2013 8:06 am

Slugger, if you know that your users are happy and that everyone has a fresh data grab (sure, I could check the logs, but what's the fun in that) then I'm going to sync the API so that production is 20130224. I got side-tracked with the new data import issues with our upstream, but that's going to have to be a longer term fix.

In the meantime, I'm going to switch gears and do more work on the metadata. Reports on the mythtv-users mailing list show that thetvdb is having problems again, so seems like as good a time as any to get the alternate metadata integrated from epguide.com

Post Reply