<?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>When framework designers outsmart themselves [How to: Perform streaming HTTP uploads with .NET]</title><link>http://blogs.msdn.com/b/delay/archive/2009/09/08/when-framework-designers-outsmart-themselves-how-to-perform-streaming-http-uploads-with-net.aspx</link><description>As part of a personal project, I had a scenario where I expected to be doing large HTTP uploads (ex: PUT ) over a slow network connection. The typical user experience here is to show a progress bar, and that's exactly what I wanted to do. So I wrote some</description><dc:language>en</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: When framework designers outsmart themselves [How to: Perform streaming HTTP uploads with .NET]</title><link>http://blogs.msdn.com/b/delay/archive/2009/09/08/when-framework-designers-outsmart-themselves-how-to-perform-streaming-http-uploads-with-net.aspx#10173476</link><pubDate>Fri, 10 Jun 2011 20:12:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10173476</guid><dc:creator>David Anson</dc:creator><description>&lt;p&gt;Cory,&lt;/p&gt;
&lt;p&gt;Wow, thanks for letting me know! Filing a report on Connect with a detailed demonstration of the problem (like you did) is exactly the right thing to do. I&amp;#39;m sure the right folks will look into this soon.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10173476" width="1" height="1"&gt;</description></item><item><title>re: When framework designers outsmart themselves [How to: Perform streaming HTTP uploads with .NET]</title><link>http://blogs.msdn.com/b/delay/archive/2009/09/08/when-framework-designers-outsmart-themselves-how-to-perform-streaming-http-uploads-with-net.aspx#10173465</link><pubDate>Fri, 10 Jun 2011 19:35:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10173465</guid><dc:creator>Cory</dc:creator><description>&lt;p&gt;There&amp;#39;s a bug in Silverlight&amp;#39;s implementation of this. If the request stream gets closed by the server, Silverlight will deadlock on a call to Write to it, if AllowWriteStreamBuffering has been set to false.&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a full example attached to this bug report (just expand the Details section):&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="https://connect.microsoft.com/VisualStudio/feedback/details/674960/writing-to-ms-internal-internalwebrequeststream-deadlocks-when-host-closes-request-stream#details"&gt;connect.microsoft.com/.../writing-to-ms-internal-internalwebrequeststream-deadlocks-when-host-closes-request-stream&lt;/a&gt;&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10173465" width="1" height="1"&gt;</description></item></channel></rss>