Awesome, finally understand how Scheduler.Now is used, when I first saw that in Rx I knew you guys were using (or planning on using) virtual time but there seemed to be no documentation anywhere on the subject. Thanks for the explanation guys, extremely
useful. Eagerly waiting on your unit tests so that I can start writing my asynchronous unit tests like that!
I just realised I can write unit tests that simulate "hot" observables that I don't normally have control over i.e. mouse moves etc, I can replace the original source with a mock observable that raises events a pre-determined times and pushes them through
a virtual scheduler. Excellent!
My understanding is that the Dispose() method is more compositional than unsubscribe because if your code doesn't call unsubscribe, the .NET Framework Garbage collector will do it for you (eventually). This can help alleviate issues that Event handlers suffer
from, where if you do a += handler and not a -= handler it won't leak memory. Also Dispose() is called automatically when the IObservable completes or errors.
Glad to hear that CardSpace v2 is going to be streamlined, the user experience for v1 was extremely jarring and complicated. IMHO using an InfoCard has to be easier than entering a UserName and Password before it will get widespread adoption on the web.
Last year I attempted to implement an STS with WCF, only to throw my hands up in disgust and build my own simple authentication protocol in the end. (which i'm sure I got wrong in one way or another). I'm glad that Geneva will be making life a lot simpler
in that respect too.
I'd like to hear feedback on whether anyone thinks these protocols will get widespread adoption in the web arena, considering OAuth being a simpler (and somewhat flawed) model, seems to be getter more adoption by websites?
I'm glad named and optional parameters are added to C# 4.0. But can someone explain the syntax for named parameters. Why do they use a colon : rather than an equals? e.g. GenerateChart(copyToWord = true);
Something that always bugged me about browsers such as Firefox was that the rendering of certain elements with CSS would flicker and change with a mouse hover, even when the css had no mention of mouse events. Obviously this
was due to the way they managed CSS internally. IE6 and 7 were always the exception to this, if something rendered and you hovered, that's the way it stayed. I was quite worried to see IE8 fall into to this strange habit (admittedly perhaps the CSS was poorly
written, but it's not the point, it shouldn't flicker and change once rendered). Could you perhaps explain why IE8 works this way?