<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>WDFREQUESTs are not for sharing</title><link>http://blogs.msdn.com/doronh/archive/2009/03/04/wdfrequests-are-not-for-sharing.aspx</link><description>FYI: this is a bit of a long post, but I wanted to be thorough and illustrative and give some insight into how the framework works and potential design that could have been made, but were not for the sake of simplicity and performance A common misconception</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>WDFREQUESTs are for sharing in KMDF v1.9</title><link>http://blogs.msdn.com/doronh/archive/2009/03/04/wdfrequests-are-not-for-sharing.aspx#9460772</link><pubDate>Fri, 06 Mar 2009 00:48:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9460772</guid><dc:creator>A Hole In My Head</dc:creator><description>&lt;p&gt;In my last post I described why a WDFREQUEST is unique to a particular WDFDEVICE.&amp;amp;#160; There is one&lt;/p&gt;
</description></item></channel></rss>