Wes Dyer: Controlling Concurrency in Rx | Rx Dev Videos

Richard.Hein
... my guitar gently weeps ...

"Now this thing ... is loathsome. Besides being loathsome, it is also ..." I can't wait for the opportunity to use this line. Big Smile

This solution looks great ... I was thinking about time too and when you mentioned the TestScheduler it was right with my train of thought - virtualized time. Can you vary the frequency of threads separately, or in groups - like if you know certain operations can go off and run as fast as possible, or if you were accessing some network resources and you want to buffer certain results etc...? It's like quantization of sorts isn't it? I mean, you take a set of concurrent operations which are continuous in "wall time" and isolate them together into there own discrete time, so I think quantization fits, no?

Wes Dyer

In reply to Richard.Hein

#Dec 18th, 2009 @ 9:05 PM

You certainly could vary the speed of "virtual threads" independently. We have only begun to investigate the possibilities here. I encourage you to play around with it and see what you can come up with.

cdwatkins

Well done, this is very nice. Makes me really want to start using Rx more.

Flynn0r
Passionate about code

Incredible work.

officework

I wonder if someone from the team could give us a hint as to whether Rx is likely to get a release with a license that would allow its commercial use? Hopefully it won't be kept "testing only" until it's rolled into .Net 5, or whatever!

Car Leasing

windowslover

I am currently running the new version of the Attendance Rx software and i like the remarquable changes like replacing Observable.Context by Schedulers and DateTimeOffset instead of DateTime...i want to express my deeply gratitude to the developers team Greeting , Sam.

Voucher Codes | Seo Company | FM jobs