GetAsync is already async - so is ReadAsStringAsync.
I explicitly tried to bind them closely together with things I found in the Task Category (ContinueWith) instead of making use of the AsyncTask region, which I deliberately tried not to do because it didn’t seem right here.
I felt like there had to be a way to spawn the next Task in a more elegant way.
I’m still trying to get my head around how I should be thinking about vvvv.
I’m a .NET guy, so I keep thinking about starting with my .NET code and then re-writing that as nodes. Really, I should be thinking one level up, I think, piecing together blocks. But I guess you have to make those blocks first, which I would almost rather do this async code in a class library and then pull that into vvvv.
@andywestion When dealing with tasks we often wrap them in observables, as we have better support for those library wise. Patching with tasks is coming up more frequently, see also the quest here https://github.com/vvvv/VL-Language/issues/25
And yes there’s nothing wrong with writing your “blocks” in C# and piecing them together in VL.