ajax - ASP.Net MVC: Creating an Area for json requests -
Just what people think about creating an area to capture / manage Jason based requests (note I mostly I'm not receiving the data). I know this is not a general use of your area (i.e., you usually create a separate area for blog vs. forum), but I'm going to the point where my project is not big, but definitely i There are many things in Jason's luggage that confuse the issue and things have to be "unclean". For example, in the lower part of each controller where I'm putting Jason actions and not mixed with other actions, I give them a prefix with Jason - I should not have to do this ... besides me There are specific visual models for JSON, which I also have to give prefix with Jason ... etc etc etc
It would be very cleaner in their area. To stop and json prefix to be able to be defined by leaving together and that area ... What do you think or is it a bad idea?
Cheers Anthony
I think this is a good idea. Where there is such an asynchronous area where all controllers implement only asynchronous tasks, they will definitely clean your code. The problem will come when your project will become so big that you want to expand in the regular areas, then you will end up with some naming conventions, which can be confusing.
Comments
Post a Comment