Comments on: WOE “GeoPlanet”: HTTP/1.1 406 Not Acceptable http://laughingmeme.org/2008/11/19/woe-geoplanet-http11-406-not-acceptable/ Just another WordPress weblog Wed, 10 Mar 2010 15:18:40 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Kellan http://laughingmeme.org/2008/11/19/woe-geoplanet-http11-406-not-acceptable/comment-page-1/#comment-615579 Kellan Thu, 20 Nov 2008 17:45:10 +0000 http://laughingmeme.org/?p=4087#comment-615579 <p>Hey Mike,</p> <p>The documentation I read said this:</p> <p>"The API is accessed via HTTP GET.</p> <p>Examples</p> <p>Find the WOEID of a significant landmark: http://where.yahooapis.com/v1/places.q('sydney%20opera%20house')?appid=[yourappidhere]" "</p> <p>I don't think I should have to read any more then that to make a simple API call. Nowhere in there is there a mention of "this will break if you don't use the full feature set of an HTTP 1.1 compliant HTTP client". In fact the implication is quite the opposite. </p> <p>But yeah, mostly the lack of a default is just brain damage, RESTful brain damage :)</p> Hey Mike,

The documentation I read said this:

“The API is accessed via HTTP GET.

Examples

Find the WOEID of a significant landmark: http://where.yahooapis.com/v1/places.q(’sydney%20opera%20house’)?appid=[yourappidhere]” “

I don’t think I should have to read any more then that to make a simple API call. Nowhere in there is there a mention of “this will break if you don’t use the full feature set of an HTTP 1.1 compliant HTTP client”. In fact the implication is quite the opposite.

But yeah, mostly the lack of a default is just brain damage, RESTful brain damage :)

]]> By: Mike Malone http://laughingmeme.org/2008/11/19/woe-geoplanet-http11-406-not-acceptable/comment-page-1/#comment-614917 Mike Malone Thu, 20 Nov 2008 00:42:00 +0000 http://laughingmeme.org/?p=4087#comment-614917 <p>To be fair, the documentation does say it defaults to whatever's specified in the accept-header ;). It probably makes sense to have a default-default too though because, yaknow, why not? The bigger question is: why use xml when json fits the same amount of awesome in a smaller, quickly parsed, and more comprehensible package?</p> To be fair, the documentation does say it defaults to whatever’s specified in the accept-header ;) . It probably makes sense to have a default-default too though because, yaknow, why not? The bigger question is: why use xml when json fits the same amount of awesome in a smaller, quickly parsed, and more comprehensible package?

]]>