Comments for Zero Bug Build

Comment on Detecting disconnected clients the Rx way by Jesus Nunez

Jesus Nunez — Thu, 31 Aug 2017 10:15:43 +0000

Pretty well explained, great work over there! You could perhaps make a second part explaining your thoughs on how to handle the lifecycle of the heartbeat itself in the client side. Keep it up!

Comment on Rx Hammer-Nail Syndrome by Todd

Todd — Thu, 09 Apr 2015 23:04:14 +0000

You have changed.. Everything is a stream. Everything!

Comment on Get a .gitignore file for Visual Studio fast with gitignore.io and Powershell by Alexander Batishchev

Alexander Batishchev — Wed, 08 Oct 2014 02:34:09 +0000

The site works terribly in Chrome for Android. And has the same issue as GitHub: C# .NET is called Visual Studio by some reason.

Comment on Comparing previous and current items with Rx by James World

James World — Mon, 06 Oct 2014 23:10:28 +0000

Nice idea. I never liked exposing Tuple but wanted to keep the concept count low for the post. This is a good compromise between flexibility and ease of use, I like it.

Comment on Comparing previous and current items with Rx by Charles Rice

Charles Rice — Mon, 29 Sep 2014 18:58:20 +0000

I liked your extension but I think you could make the signature better. if you make the signature public static IObservable WithPrevious(this IObservable source, Func projection)

Then you can hide the tuple. You just need to change the code to be

return source.Scan(new Tuple(default(TSource), default(TSource)),
(previous, current) => Tuple.Create(previous.Item2, current))
.Select(t => projection(t.Item1, t.Item2));

Now there is no tuple exposed and the projection is handled. It makes using it a lot nicer were you just pass in a Func that takes the previous and current and does whatever it needs to do.

But this is a real good solution to use scan.

Comment on Rx Hammer-Nail Syndrome by Daniel Fernandes

Daniel Fernandes — Fri, 28 Mar 2014 08:20:21 +0000

Isn’t Mike’s blog assuming a progressive and possibly controllable via the stream consumer fetching of pages therefore making Rx most suitable in his example ?
Seems to me that Reactive Programming in general is better aligned to how things work but it can get unnecessary complicated quickly.

Comment on Detecting disconnected clients the Rx way by James World

James World — Fri, 07 Jun 2013 19:14:13 +0000

There isn’t really a meaningful use for OnCompleted in this scenario – it’s designed as a non-terminating stream. In this sample application the while loop is just there to keep things running and feed the query for demo purposes; in a production situation you would create the subscription in start-up code an then just let it run, and make the OnNext calls from whatever service code is handling client calls (e.g. perhaps some web service logic). The Disposable of the subscription is all you need to stop monitoring clients – and it’s not even essential to call that unless you want to stop monitoring separately from shutting down your application.

Comment on Detecting disconnected clients the Rx way by mabra

mabra — Sun, 02 Jun 2013 13:49:11 +0000

Hello !
Really nice, something I have to understand…. [RX is too complicated to mee ].
In your exit decision [after "q"], I just inserted this:
clientHeartbeats.OnCompleted();
and in the subscription registration, I added a handler for OnComplete. This works, for the first view.
But:After I enter “q” and the timeout was NOT reached,
I am getting “disconnected” messages for each client.
I feel bad with this and I do not understand why.

Would be nice, if this can be described.

Thanks anyway and
best regards,
++mabra

Comment on Dealing with occasionally overrunning Timer initiated tasks using recursive scheduling by James World

James World — Fri, 24 May 2013 15:27:43 +0000

Cheers Morgan, watch out for the next installment – when things will get more interesting and even RegisterWaitForSingleObject will start to struggle…

Comment on Dealing with occasionally overrunning Timer initiated tasks using recursive scheduling by Morgan

Morgan — Fri, 24 May 2013 14:47:51 +0000

For anyone not using Rx you can use the most excellent yet forgotten/misunderstood RegisterWaitForSingleObject API. It’s a thing of beauty.

http://blogs.msdn.com/b/morgan/archive/2008/12/18/periodic-execution-in-net.aspx