AsyncRequestDispatcher in ASP.NET MVC

[shapper]

Hello,

I have been using RequestDispatcher in a MVC project.

Can I use an AsyncRequestDispatcher? In this case do I need to use an AsynController?

Using an AsyncRequestDispatcher implies that the controller might return the view before the Response is received?

Or this only happens when using an AsyncRequestDispatcher with an AsyncController?

---
 
Thank You,
Miguel


[Deathraven]

The AsyncRequestDispatcher has nothing todo with http request that your
Controller might recieve.

[Mark Meyers]

in an mvc context it is probably better to run agatha in process imho

[shapper]

Hello,

Yes, if I understood you correctly, that is what I am using.

I am using Client with no WCF and using RequestDispatcher:

new ServiceLayerAndClientConfiguration(typeof(MyHandler).Assembly, typeof(MyRequest).Assembly, new Agatha.StructureMap.Container(ObjectFactory.Container)).Initialize();

FindUserByIdResponse response = _dispatcher.Get<FindUserByIdResponse>(request);

What about having two packages: a base one and and extra one for WCF?

--- 
Thank You,
Miguel

[Mark Meyers]

What about having two packages: a base one and and extra one for WCF?

this might help

not sure if I understand the advantage to using an AsyncRequestDispatcher in this context, you will have to wait for the agatha-response anyway before you can return the http-response (view)

[Mark Meyers]

elaborating : I can't imagine a scenario where a user would be willing to wait that long for a page, so that this kind of infrastructure would be required in order to free up some threads ;-)

[Davy Brion]

the only benefit i see from using an asyncrequestdispatcher in a web context is if you need to send multiple, independent calls to *separate* services and you just want to minimize the total wait time.  Other than that, there's no benefit to using the asyncrequestdispatcher in a web context IMO.

[shapper]

Thank You Both for the feedback,

Miguel