[Mono-dev] PR #1365: [asp.net] Implement the EventHandlerTaskAsyncHelper and HttpTaskAsyncHandler classes
Miguel de Icaza
miguel at xamarin.com
Sun Oct 26 17:24:32 UTC 2014
I am purely provided some background for interested hackers.
I stand by the original position that we should do all the minimal changes
required to get ASP.NET vnext to build/run, even if it does not deliver the
performance/scaling benefits at first.
As for the actual patch, I will review once I am back on my computer
On Sun, Oct 26, 2014 at 9:50 AM, Martin Thwaites <monoforum at my2cents.co.uk>
> Hi Miguel,
> Does that have implications in regards to this PR? i.e. is it just that it
> doesn't solve the problem, or that the implementation here is wrong?
> On 26 October 2014 13:46, Miguel de Icaza <miguel at xamarin.com> wrote:
>> The asynchronous pipeline was discussed in various blogs/interviews.
>> Some switch enables apparently an entirely different flow inside asp.net.
>> The surface changes were minimal, which is why you won't likely find an API.
>> On Sunday, October 26, 2014, Kornel Pal <kornelpal at gmail.com> wrote:
>>> Inspired by the ASP.NET 4.5 Async Pipeline email thread started by
>>> Martin Thwaites, I realized that there actually is no new async pipeline in
>>> ASP.NET 4.5, it merely provides wrappers around tasks to ease
>>> interfacing with the old async pipeline.
>>> I've looked around a bit, but found no suitable implementation for the
>>> wrapper, so I've created several unit tests to figure out the MS.NET
>>> behavior. At the end I came up with TaskAsyncResult, a general purpose TAP
>>> to APM wrapper.
>>> Please review my pull request: https://github.com/mono/mono/pull/1365
>>> Thank you.
>>> Mono-devel-list mailing list
>>> Mono-devel-list at lists.ximian.com
>> 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