[Mono-dev] ASP.NET 4.5 Async Pipeline
monoforum at my2cents.co.uk
Wed Oct 22 15:42:34 UTC 2014
That is a great idea around making them synchronous in the background. I'm
sure this would cause some issues for people, however if we can hit the
main use cases in the initial stab that would be great.
Are you suggesting that this is done in the Webapi code, or somewhere in
the mono source. My goal has been to make it so we don't need our own
implementation of the aspnetwebstack. It would also be great if we can say
that async controllers work in mono, just run synchronously, rather than
"use these dlls and Webapi will work".
Thanks for offering to help out, if there is some initial Google terms you
could point me in the direction of that would be great as Async pipeline
doesn't seem to be specific enough.
On 22 Oct 2014 14:58, "Miguel de Icaza" <miguel at xamarin.com> wrote:
> You could start by "faking" the async controllers for now. This would be
> enough to support WebAPI, even if behind the scenes it is entirely sync.
> This buys us some time to research the subject. There were a few
> interesting posts on MSDN, and the blogs about how this works a couple of
> years ago, so those would be great research material.
> I can assist (in my copious spare time) with this, as I wrote chunks of
> the current ASP.NET pipeline with Gonzalo.
> On Tue, Oct 21, 2014 at 4:02 PM, Martin Thwaites <monoforum at my2cents.co.uk
> > wrote:
>> Hi all,
>> I'm still working through implementing methods to mvc/webapi, however,
>> I've found that the newer versions of WebApi are reliant on async
>> Now, my perception is that this means that the note on the mono
>> compatibility page around the Async Pipeline needs to be implemented for
>> that to work. First, please let me know if I've misunderstood.
>> If I take this on, I'm going to need some help to implement it. I see 2
>> options, first, someone helps me out with some resources that I can use to
>> devise a way to do it, articles on the process, examples of where it might
>> be implemented in the current codebase for other things, etc. Second, we
>> enlist the help of someone who is more equipped.
>> I believe that there are quite a few people who are interested in getting
>> this implemented, and therefore I have an idea that we could potentially
>> crowd fund the money to pay a contractor to potentially do it. My hope
>> would be that with a financial incentive, someone within Xamarin may be
>> willing to put forward their spare time to do it. This would likely give
>> us a better chance of getting it merged due to them already being used
>> Miguel's (understandably high) standards and the processes involved in
>> So, is there anybody else who would be willing to donate to this (I'm
>> thinking something like a kickstarter campaign so that people can get their
>> money back if it doesn't go ahead).
>> Also, does anyone who has an idea of how it would be done have any idea
>> what sort of effort we would be looking at?
>> Alternatively, can someone give me an idea of where to start with
>> implementing it?
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list