<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Device Atlas API and Django-Admob</title>
	<atom:link href="http://johnboxall.ca/2009/01/26/deviceatlas-api-and-django-admob/feed/" rel="self" type="application/rss+xml" />
	<link>http://johnboxall.ca/2009/01/26/deviceatlas-api-and-django-admob/</link>
	<description>Genius billionaire playboy web developer.</description>
	<pubDate>Thu, 29 Jul 2010 17:15:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: john</title>
		<link>http://johnboxall.ca/2009/01/26/deviceatlas-api-and-django-admob/comment-page-1/#comment-191</link>
		<dc:creator>john</dc:creator>
		<pubDate>Tue, 24 Feb 2009 03:00:32 +0000</pubDate>
		<guid isPermaLink="false">http://johnboxall.ca/?p=69#comment-191</guid>
		<description>@versae DeviceAtlas has had a Python API for some time though 2.3 compatibility is still in the works:
http://deviceatlas.com/downloads/beta

Thanks for the link to the W3C simple API - I find it interesting that these methods appear verbatim in the original Device Atlas API. Most (web) programmers are looking for higher level functionality from their device library - for example - what kind of video is optimal to serve to this phone? While you can get this information by querying a number of properties on WURFL or Device Atlas, an ideal library would present these most common use cases as higher level functions!

Cheers,

John</description>
		<content:encoded><![CDATA[<p>@versae DeviceAtlas has had a Python API for some time though 2.3 compatibility is still in the works:<br />
<a href="http://deviceatlas.com/downloads/beta" rel="nofollow">http://deviceatlas.com/downloads/beta</a></p>
<p>Thanks for the link to the W3C simple API - I find it interesting that these methods appear verbatim in the original Device Atlas API. Most (web) programmers are looking for higher level functionality from their device library - for example - what kind of video is optimal to serve to this phone? While you can get this information by querying a number of properties on WURFL or Device Atlas, an ideal library would present these most common use cases as higher level functions!</p>
<p>Cheers,</p>
<p>John</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: versae</title>
		<link>http://johnboxall.ca/2009/01/26/deviceatlas-api-and-django-admob/comment-page-1/#comment-157</link>
		<dc:creator>versae</dc:creator>
		<pubDate>Sat, 14 Feb 2009 01:44:39 +0000</pubDate>
		<guid isPermaLink="false">http://johnboxall.ca/?p=69#comment-157</guid>
		<description>I never knew that there was DeviceAtlas API for Django, so far I have been using WURFL in djangobile (http://code.google.com/p/djangobile/), but I would like DeviceAtlas formed part of procces of device detection.
Although the ideal would be to implement the interface proposed by the W3C (http://www.w3.org/TR/2008/PR-DDR-Simple-API-20080917/).</description>
		<content:encoded><![CDATA[<p>I never knew that there was DeviceAtlas API for Django, so far I have been using WURFL in djangobile (http://code.google.com/p/djangobile/), but I would like DeviceAtlas formed part of procces of device detection.<br />
Although the ideal would be to implement the interface proposed by the W3C (http://www.w3.org/TR/2008/PR-DDR-Simple-API-20080917/).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
