[SPIKE] Async API from Highlevel

[danielmarbach]

DO NOT MERGE

Opposed to #149 this PR aims to explore an async API from a high level perspective first. Instead of changing low level infrastructure like NetworBinaryWriter it starts from IModel.

The idea of this spike is to show that we can stay as true as possible to the current API design and "just" make it async enabled without requiring a whole lot of new API design changes

@michaelklishin thoughts?

[michaelklishin]

Thank you! We're quite busy this week, will get to this PR eventually.

[danielmarbach]

Don't worry. Enjoying my life on thailand. Take your time

Am 13.01.2016 um 17:54 schrieb Michael Klishin [email protected]:

Thank you! We're quite busy this week, will get to this PR eventually.

—
Reply to this email directly or view it on GitHub.

[danielmarbach]

I'm back from Thailand and hopefully more responsive

Am 13.01.2016 um 11:54 schrieb Michael Klishin [email protected]:

Thank you! We're quite busy this week, will get to this PR eventually.

—
Reply to this email directly or view it on GitHub.

[michaelklishin]

Thanks. Unfortunately we are still quite jammed.

[danielmarbach]

@michaelklishin ping me when you want me to help you guys out move the async/await initiative forward

[michaelklishin]

@danielmarbach we will, thank you. I'm going to post a plan for the .NET client on Monday or so next week.

[michaelklishin]

I've recently reviewed this with someone and will close this and post some thoughts about our plan to #83. Thank you very much for providing this spike PR, it's influenced our thinking on the subject.