<?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: API keys (tokens) to track api usage</title>
	<atom:link href="http://depts.washington.edu/ontheroa/?feed=rss2&#038;p=380" rel="self" type="application/rss+xml" />
	<link>http://depts.washington.edu/ontheroa/?p=380</link>
	<description>The UW blog for all things Resource Oriented Architecture &#38; web services - email appdev@u.washington.edu</description>
	<lastBuildDate>Tue, 07 Feb 2012 00:23:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: ttchang</title>
		<link>http://depts.washington.edu/ontheroa/?p=380&#038;cpage=1#comment-189</link>
		<dc:creator>ttchang</dc:creator>
		<pubDate>Wed, 10 Mar 2010 22:22:23 +0000</pubDate>
		<guid isPermaLink="false">http://depts.washington.edu/ontheroa/?p=380#comment-189</guid>
		<description>Good question. No nothing specific in terms of implementation just that we thought it would be best placed in the uri. We figured we should determine if we should make the use of a key part of our WS policy first before we figured out a design.</description>
		<content:encoded><![CDATA[<p>Good question. No nothing specific in terms of implementation just that we thought it would be best placed in the uri. We figured we should determine if we should make the use of a key part of our WS policy first before we figured out a design.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Prohaska</title>
		<link>http://depts.washington.edu/ontheroa/?p=380&#038;cpage=1#comment-188</link>
		<dc:creator>Gary Prohaska</dc:creator>
		<pubDate>Wed, 10 Mar 2010 18:57:30 +0000</pubDate>
		<guid isPermaLink="false">http://depts.washington.edu/ontheroa/?p=380#comment-188</guid>
		<description>Given that the recommendation is for optional use by web service consumers I think this is a valuable change and imo potential benefits outweigh the costs.

Question: was their any discussion about &quot;how&quot; the api key would be embedded in the URI?</description>
		<content:encoded><![CDATA[<p>Given that the recommendation is for optional use by web service consumers I think this is a valuable change and imo potential benefits outweigh the costs.</p>
<p>Question: was their any discussion about &#8220;how&#8221; the api key would be embedded in the URI?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Stephenson</title>
		<link>http://depts.washington.edu/ontheroa/?p=380&#038;cpage=1#comment-179</link>
		<dc:creator>Scott Stephenson</dc:creator>
		<pubDate>Thu, 04 Mar 2010 19:14:56 +0000</pubDate>
		<guid isPermaLink="false">http://depts.washington.edu/ontheroa/?p=380#comment-179</guid>
		<description>I think we should do this.  It&#039;s a win-win scenario.</description>
		<content:encoded><![CDATA[<p>I think we should do this.  It&#8217;s a win-win scenario.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Lewis</title>
		<link>http://depts.washington.edu/ontheroa/?p=380&#038;cpage=1#comment-164</link>
		<dc:creator>Tom Lewis</dc:creator>
		<pubDate>Wed, 24 Feb 2010 21:47:23 +0000</pubDate>
		<guid isPermaLink="false">http://depts.washington.edu/ontheroa/?p=380#comment-164</guid>
		<description>If the costs are not really burdensome, then this sounds like a great approach.</description>
		<content:encoded><![CDATA[<p>If the costs are not really burdensome, then this sounds like a great approach.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
