Search found 20 matches

by hall5714
Wed Mar 06, 2013 8:46 pm
Forum: Developer
Topic: Developer Wishlish for new JSON API
Replies: 50
Views: 79248

Re: Developer Wishlish for new JSON API

{"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?
by hall5714
Fri Mar 01, 2013 11:45 am
Forum: Developer
Topic: Developer Wishlish for new JSON API
Replies: 50
Views: 79248

Re: Developer Wishlish for new JSON API

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.
by hall5714
Thu Feb 28, 2013 5:22 pm
Forum: Developer
Topic: Developer Wishlish for new JSON API
Replies: 50
Views: 79248

Re: Developer Wishlish for new JSON API

Sorry, this has been a bit of a hectic week, I'll get the python client updated this weekend with the changes.
by hall5714
Mon Feb 25, 2013 5:31 pm
Forum: Developer
Topic: Developer Wishlish for new JSON API
Replies: 50
Views: 79248

Re: Developer Wishlish for new JSON API

Now that I've figured out how to do it with the metadata, I can probably do it for everything. Would that be better? The API version thing isn't hard-and-fast; as long as external clients are using it yet, then it's just a "number". Obviously I'd like it to be "done" at some point so that I can fin...
by hall5714
Mon Feb 25, 2013 9:15 am
Forum: Developer
Topic: Developer Wishlish for new JSON API
Replies: 50
Views: 79248

Re: Developer Wishlish for new JSON API

Posted this on the other thread, so I'll summarize here: I've changed the "get" "metadata" response on the test server: {"randhash":"60610a5d8d41de88450a4196a0f7b9dd","object":"metadata","action":"get","api":20130224} Response from server: {"response":"OK","code":200,"serverID":"AWS-micro.1","messa...
by hall5714
Mon Feb 25, 2013 9:12 am
Forum: Developer
Topic: Developer Wishlish for new JSON API
Replies: 50
Views: 79248

Re: Developer Wishlish for new JSON API

I don't think much of any of this looks like a RESTful service. If it did, I'd be inclined to agree with you. However, this whole service works on sending requests to request.php and getting back responses. And request.php (the lone resource) always exists so unless the Apache server is ill, Apache...
by hall5714
Mon Feb 25, 2013 12:01 am
Forum: Developer
Topic: Developer Wishlish for new JSON API
Replies: 50
Views: 79248

Re: Developer Wishlish for new JSON API

Robert's explanation was perfect. Only because the error codes the API generates appear to be the same as HTTP status codes, but in reality they aren't. The HTTP status code should reflect the status of the web server itself and when it's behaving as expected, it should only ever return 2xx status ...
by hall5714
Sun Feb 24, 2013 9:52 am
Forum: Developers Corner
Topic: Alpha version of new Schedules Direct lineup information
Replies: 28
Views: 340558

Re: Alpha version of new Schedules Direct lineup information

RobNewton wrote:@Hall - thanks, that should give a huge head sart. Much appreciated. If I have any improvements during my development, I'll fork it and send you a pull request.
Thanks Rob!
by hall5714
Sun Feb 24, 2013 9:49 am
Forum: Developer
Topic: Developer Wishlish for new JSON API
Replies: 50
Views: 79248

Re: Developer Wishlish for new JSON API

- earlier versions of the code did this. It would be relatively simple to put it back. If the other active developers can weigh in, I can make the change. The thought was that I wanted to differentiate between response codes from the API and apache response codes; if apache dies for whatever reason...
by hall5714
Fri Feb 22, 2013 11:25 am
Forum: Developer
Topic: Developer Wishlish for new JSON API
Replies: 50
Views: 79248

Re: Developer Wishlish for new JSON API

Posted this on the other thread, so I'll summarize here: (1) Send HTTP response codes when an error occurs. IE: Incorrect password should send an HTTP 401, etc. Since the JSON response is already including HTTP codes, this should be a simple matter of header('X-Response-Code: 404', true, 404); (or h...