workflow - Guidance Needed for WF and Parallelism in ASP.Net -
The more I search for certain topics in relation to ASP.net, the more I think how and where the ASP TNN.T.T. To implement certain things correctly in realm (both webforms and mvc)
Workflow Foundation
I like to use WF; However, what I have read is that it is not recommended for ASP.NET app due to 1 workflow hosting environment, according to the App Domain restriction. Now I have not seen where this restriction has changed but after the old DNS 3.0 (.netfx) days I still can not find any information about this restriction. I'm looking for advice to create workflow in services which looks good; However, there are not such exact same limitations, where the service is often hit repeatedly, will it result in some performance issues? Is there a place for WF in ASP.net and if so, where?
Parallel processing
The same thing for the sake of the same thing because of the method of setting up a thread pool in the application pool of IIS, I always have multi-threaded ASP Net applications have been viewed / read. Now with Net4 and with multi-core processors everywhere, multi-threading is again one of the hottest topics. I like what I see in parallel extensions in 4.0; However, is this advice still not in ASP.net or are there some places where it will be recommended at this point?
Is there advice still on these two items from the year before? Should not they still be in ASP.NET world?
Thanks
Multicast is quite irrelevant in ASP.net - the reason for it That any code writing in ASP.NET is meant to handle the same request. There are two main reasons for using multiple threads in other types of applications:
- Another thread works, while updating the URI - the user does not have anything on the web app Unless the whole work is done
- Better performance by using all available cores - other cores do not have much advantage if other users are not busy with the requests.
The workflow has been designed for a long time, the ongoing work - do not use it, where the button on the button will have to do some simple code. Remove the need for an immediate reaction and a simple queue takes care of the most probable performance problems. I have used WF inside ASP.Net pages, but if I need speed or a large number of users, then I will not do this.
Comments
Post a Comment