<?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: Jared Allen Lookin&#039; Straight Barney = The Future?</title>
	<atom:link href="http://arrowheadaddict.com/2008/04/18/jared-allen-lookin-straight-barney-the-future/feed/" rel="self" type="application/rss+xml" />
	<link>http://arrowheadaddict.com/2008/04/18/jared-allen-lookin-straight-barney-the-future/</link>
	<description>A Kansas City Chiefs Fan Site - News, Blogs, Opinion and more</description>
	<lastBuildDate>Fri, 25 May 2012 00:18:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: John</title>
		<link>http://arrowheadaddict.com/2008/04/18/jared-allen-lookin-straight-barney-the-future/#comment-13366</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 21 Apr 2008 02:41:09 +0000</pubDate>
		<guid isPermaLink="false">http://arrowheadaddict.com/2008/04/18/jared-allen-lookin-straight-barney-the-future/#comment-13366</guid>
		<description>CORRECTION:

My Bad!  Vikes&#039; 2nd rd. pick this year is #47, not #43, which would be equivalent to a R1 #15 pick in 2009.  Believe the conclusion still holds, even if the numbers area little less strong.</description>
		<content:encoded><![CDATA[<p>CORRECTION:</p>
<p>My Bad!  Vikes&#8217; 2nd rd. pick this year is #47, not #43, which would be equivalent to a R1 #15 pick in 2009.  Believe the conclusion still holds, even if the numbers area little less strong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jason</title>
		<link>http://arrowheadaddict.com/2008/04/18/jared-allen-lookin-straight-barney-the-future/#comment-13365</link>
		<dc:creator>jason</dc:creator>
		<pubDate>Sun, 20 Apr 2008 22:46:20 +0000</pubDate>
		<guid isPermaLink="false">http://arrowheadaddict.com/2008/04/18/jared-allen-lookin-straight-barney-the-future/#comment-13365</guid>
		<description>right there with ya john</description>
		<content:encoded><![CDATA[<p>right there with ya john</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://arrowheadaddict.com/2008/04/18/jared-allen-lookin-straight-barney-the-future/#comment-13364</link>
		<dc:creator>John</dc:creator>
		<pubDate>Sun, 20 Apr 2008 22:40:25 +0000</pubDate>
		<guid isPermaLink="false">http://arrowheadaddict.com/2008/04/18/jared-allen-lookin-straight-barney-the-future/#comment-13364</guid>
		<description>Adam:

To change the tone a bit, actually I would prefer the Vikes #17 and #43 this year to their #17 this year and their unknown Round 1 pick in 2009.  Due to Pats R1 forfeit this year, #43  is equivalent to the the 11th pick in R2.  If you accept that a &quot;bird in the hand&quot; this year is one round more valuable than the same pick next year, then the Vikes would have to be giving up the equivalent of pick #11 in next year&#039;s Round 1; possible but not likely since they are picking #17 this year and would have the benefit of Allen next year.  Also, you have to believe next year&#039;s draft will be as strong as this year&#039;s, again possible but not likely.  My first choice would be to work out a long term contract with Allen.  If this is not possible, then take the Vike&#039;s #17 and #43 this year and RELOAD with at least 12 picks (maybe more with trades down)in this year&#039;s strong/deep draft!</description>
		<content:encoded><![CDATA[<p>Adam:</p>
<p>To change the tone a bit, actually I would prefer the Vikes #17 and #43 this year to their #17 this year and their unknown Round 1 pick in 2009.  Due to Pats R1 forfeit this year, #43  is equivalent to the the 11th pick in R2.  If you accept that a &#8220;bird in the hand&#8221; this year is one round more valuable than the same pick next year, then the Vikes would have to be giving up the equivalent of pick #11 in next year&#8217;s Round 1; possible but not likely since they are picking #17 this year and would have the benefit of Allen next year.  Also, you have to believe next year&#8217;s draft will be as strong as this year&#8217;s, again possible but not likely.  My first choice would be to work out a long term contract with Allen.  If this is not possible, then take the Vike&#8217;s #17 and #43 this year and RELOAD with at least 12 picks (maybe more with trades down)in this year&#8217;s strong/deep draft!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ComeSackMyQB</title>
		<link>http://arrowheadaddict.com/2008/04/18/jared-allen-lookin-straight-barney-the-future/#comment-13363</link>
		<dc:creator>ComeSackMyQB</dc:creator>
		<pubDate>Sun, 20 Apr 2008 18:31:21 +0000</pubDate>
		<guid isPermaLink="false">http://arrowheadaddict.com/2008/04/18/jared-allen-lookin-straight-barney-the-future/#comment-13363</guid>
		<description>i am tryin..he acts like im carl or im defending carl..i have nothing but discontent for peterson..i wanna see him gone..ive said this all before and he doesnt seem to get it</description>
		<content:encoded><![CDATA[<p>i am tryin..he acts like im carl or im defending carl..i have nothing but discontent for peterson..i wanna see him gone..ive said this all before and he doesnt seem to get it</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Object Caching 267/289 objects using apc

Served from: arrowheadaddict.com @ 2012-05-24 20:50:23 -->

<!-- W3 Total Cache: Object Cache debug info:
Engine:             apc
Caching:            enabled
Total calls:        289
Cache hits:         267
Cache misses:       22
Total time:         0.0000
W3TC Object Cache info:
    # |     Status      |     Source      | Data size (b) | Query time (s) | ID:Group
-->
