http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Bohdan, It works in .NET, but not in SL. Therefor, it is SL fault.http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment22http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment22Wed, 22 Aug 2012 10:56:39 GMTThat's not faulty Silverlight. Windows sends tcp data in segments. (And the default waiting delay is 400ms). Flush() doesn't affect NetworkStream(). There's trickery for working around that.http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment21http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment21Wed, 22 Aug 2012 10:52:25 GMTReally weird bug, if you keep the first test and the last one, everything is displayed in silverlight+ chrome ( in a VM if that matter).http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment20http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment20Sun, 29 Jul 2012 06:48:05 GMTKen, If that was what it was, I would see the same behavior in .NET and SL, but I am seeing different behavior between the two. HttpListener doesn't need to flush, it writes out immediately.http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment19http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment19Thu, 26 Jul 2012 21:01:38 GMTAn interesting thing I noticed: the call to Flush did not actually flush the stream - no network activity was noticed. I remember reading somewhere that http response stream in HttpListener are not flushing when told to. the rest of the bytes are send after the ReadLine, when the writer closes (and closes the outgoing request stream) forcing an actual flush. I tried with a comparable nodejs server script. The flush behavior there is such that to get proper progressive flushing, you need to write something, wait a little bit, and from then on it will flush every now and then (depending on its internal implementation). When I did that I started seeing the bytes actually being streamed in chunks over the wire to the client and getting there correctly. http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment18http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment18Thu, 26 Jul 2012 20:59:57 GMTNop, couldn't reproduce. Whenever request is made to "/" I get string back to silverlight and displayed in txtboxhttp://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment17http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment17Thu, 26 Jul 2012 05:54:17 GMTKen, it's TCP! Packets don't get dropped in TCP.http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment16http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment16Thu, 26 Jul 2012 05:48:19 GMTKen, We aren't disposing the server, we kep it around in the repro.http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment15http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment15Thu, 26 Jul 2012 03:37:28 GMTKen, What do you mean, takes too log? We immediately call it againhttp://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment14http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment14Thu, 26 Jul 2012 03:37:06 GMTbtw - the server dispose of the writer which probably dispose of the ctx.Response.OutputStream as well so the client is not getting any more data on the streamhttp://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment13http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment13Wed, 25 Jul 2012 22:57:41 GMTI'm not really familiar with Silverlight's web requests mechanisms, but this code looks wrong to me. it takes *way* too long for you to set up the client request to listen to the next incoming bytes, so they get dropped between the beginning of the handler to when you call read async again. did you try calling ReadAsync first? (after shortcircuiting the EOF signal)http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment12http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment12Wed, 25 Jul 2012 21:33:17 GMTGrega_g, So, you reproduced the issue without this?http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment11http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment11Wed, 25 Jul 2012 15:52:04 GMTSad to say it took me some time to figure that out...http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment10http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment10Wed, 25 Jul 2012 14:07:34 GMTIn firefox request for "/" only executes once, after that is from cache. After FF is restarted than request is made for "/" again. Looks like this:http://tinypic.com/r/5pd88/6http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment9http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment9Wed, 25 Jul 2012 14:03:13 GMTIt works even without Flush() calls. http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment8http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment8Wed, 25 Jul 2012 13:56:05 GMTGrega_g, It might be a timing issue, depending on how fast you get the data. What happens when you use just one flush?http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment7http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment7Wed, 25 Jul 2012 13:09:58 GMTworks as wellhttp://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment6http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment6Wed, 25 Jul 2012 13:06:28 GMTGrega_g, Try in IE or Chrome, those are the things I tested this withhttp://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment5http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment5Wed, 25 Jul 2012 13:03:25 GMT // Doesn't work writer.WriteLine("first"); writer.Flush(); writer.WriteLine("second"); writer.Flush(); works for me: I get "first\nsecond" in my silverlight (firefox)http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment4http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment4Wed, 25 Jul 2012 13:00:29 GMTOk, only other thing I can think of is that you could check with Wireshark if the server or client is at fault. Good luck!http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment3http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment3Wed, 25 Jul 2012 11:26:28 GMTAndomar, No, the application is still there and waiting.http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment2http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment2Wed, 25 Jul 2012 10:27:28 GMTJust a question, does the application that sends the lines quit (end its proces) right after it sends the data? Since the TCP stack is just a library, you can loose data if you ExitProcess right after sending something.http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment1http://ayende.com/157377/silverlight-streaming-the-race-condition-is-already-included#comment1Wed, 25 Jul 2012 10:24:48 GMT