http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Just saw the reference to CompositeAsyncResult, I'll check it out :) http://ayende.com/3213/async-actions-in-monorail#comment14http://ayende.com/3213/async-actions-in-monorail#comment14Tue, 01 Apr 2008 08:54:00 GMTAwesome! How can you chain several blocking operations and handlers between Begin and End? e.g. process -> (db query) -> process -> (web service) -> process -> response Anything similar to "deferred" from Twisted? (http://twistedmatrix.com/projects/core/documentation/howto/defer.html) http://ayende.com/3213/async-actions-in-monorail#comment13http://ayende.com/3213/async-actions-in-monorail#comment13Tue, 01 Apr 2008 08:44:04 GMTdimitrod, The way this is handled in RegisterAsyncTask is complex, and highly dependent on the WebForms infrastructure. Basically, they setup a time for this to catch this. Yes, we can do that, but it is not trivial. http://ayende.com/3213/async-actions-in-monorail#comment12http://ayende.com/3213/async-actions-in-monorail#comment12Sun, 30 Mar 2008 11:25:14 GMTI suggest this less verbos syntax: public AsyncEndAction Index() { IAsyncResult result = userRepository.BeginGetUserInformation(CurrentUser, ControllerContext.Async.Callback, ControllerContext.Async.State); return delegate { PropertyBag["userInfo"] = userRepository.EndGetUserInformation(result); } } http://ayende.com/3213/async-actions-in-monorail#comment11http://ayende.com/3213/async-actions-in-monorail#comment11Sat, 29 Mar 2008 19:27:18 GMTWow, that's impressing, can't wait to get it from the trunk. By the way is it possible to handle async timeouts like in the RegisterAsyncTask method? http://ayende.com/3213/async-actions-in-monorail#comment10http://ayende.com/3213/async-actions-in-monorail#comment10Wed, 26 Mar 2008 15:33:34 GMTCompositeAsyncResult :-) http://ayende.com/3213/async-actions-in-monorail#comment9http://ayende.com/3213/async-actions-in-monorail#comment9Wed, 26 Mar 2008 12:11:57 GMTAnd what if I need to make two or more WS calls? http://ayende.com/3213/async-actions-in-monorail#comment8http://ayende.com/3213/async-actions-in-monorail#comment8Wed, 26 Mar 2008 12:07:34 GMTThe standard async invocation pattern on the CLR calls for the following method signatures: BeginXyz(AsyncCallback callback, object state); EndXyz(IAsyncResult ar); You will see that in all the API that handles async actions http://ayende.com/3213/async-actions-in-monorail#comment7http://ayende.com/3213/async-actions-in-monorail#comment7Wed, 26 Mar 2008 09:13:17 GMTI'm maybe difficult today, but why do u not send in only the ControllerContext.Async to the repository on both calls and let it decide what it need from the Async object? public IAsyncResult BeginIndex() { return userRepository.BeginGetUserInformation(CurrentUser, ControllerContext.Async); } public void EndIndex() { PropertyBag["userInfo"] = userRepository.EndGetUserInformation(ControllerContext.Async); } http://ayende.com/3213/async-actions-in-monorail#comment6http://ayende.com/3213/async-actions-in-monorail#comment6Wed, 26 Mar 2008 09:08:50 GMTOpps, that is a mistake, it is supposed to be: return userRepository.BeginGetUserInf ormation(CurrentUser, ControllerContext.Async.Callback, ControllerContext.Async.State); A typo when writing the post. I fixed it, thanks for noticing http://ayende.com/3213/async-actions-in-monorail#comment5http://ayende.com/3213/async-actions-in-monorail#comment5Wed, 26 Mar 2008 08:56:29 GMTOMG this is awesome! http://ayende.com/3213/async-actions-in-monorail#comment4http://ayende.com/3213/async-actions-in-monorail#comment4Wed, 26 Mar 2008 08:40:02 GMTWhy the need for 2 calls to ControllerContext.Async.Callback in BeginGetUserInformation? return userRepository.BeginGetUserInformation(CurrentUser, ControllerContext.Async.Callback, ControllerContext.Async.Callback); Just a bug or something reasonable behind the consept? http://ayende.com/3213/async-actions-in-monorail#comment3http://ayende.com/3213/async-actions-in-monorail#comment3Wed, 26 Mar 2008 08:22:16 GMTawesome to the max http://ayende.com/3213/async-actions-in-monorail#comment2http://ayende.com/3213/async-actions-in-monorail#comment2Tue, 25 Mar 2008 23:30:25 GMTThis is a very promising new feature. Its things like this that I hope will continue to differentiate MonoRail from MS MVC. http://ayende.com/3213/async-actions-in-monorail#comment1http://ayende.com/3213/async-actions-in-monorail#comment1Tue, 25 Mar 2008 22:42:45 GMT