On which pattern are ASP.NET webforms and MVC based? PageController, FrontController? -

i trying understand asp.net webforms , mvc point of view of understanding design patterns used. while mvc looks implementation of frontcontroller, not sure webforms pages. so, appreciate if can following questions around this.

1. is webforms based on pagecontroller pattern?

2. are front controller , page controller both modified versions of mvc?

3. can webforms called special case of mvc distinction between controller , view blurred?

finally, there resources on web can provide detailed reference on topic?

following order of questions:

1//no. webforms based on the "smart ui" pattern, ie, control app writing event handlers. smart ui has issues, when entirely based on desktop works ok, in sense no major "fiction" introduced framework work. web, however, works on stateless http, major fiction introduced, in form of viewstate holds state of controls when page sent client browser. result, web forms introduce layer of complexity applications there sustain ficiton. mvc eliminates fiction.

the fiction says: pretend http not there between , client.

2//mvc removes fiction , gives naked http. more based on front controller page controller pattern in page controller pattern makes testing controller independently of http requests difficult, whereas mvc designed make controller testable independently of http requests. in other words, mvc designed enable unit testing on controllers opposed integration testing.

mvc focuses on separation of model view, whereas webforms/smart ui not make distinction.

i suppose say, eliminate page controller asp.net mvc, asp.net refactors impact of http on controllers "orthogonal attributes", not way led believe page controller pattern works. however, don't quote me on this, student of these things, not expert.

3//no not! discussed above, webforms fictional smart ui, not mvc in shape or form. can go through few hoops make them sort of mvc ish (a la dino esposito), again ficiton. why indulge in fiction if have asp.net mvc?

a final broadside. reason switched webforms mvc wizard server control. "event model" thing of cruelty flies in face of needed achieve (not mention choking proliferation of other properties, methods... yuck!).

in 10 days wrote base wizardcontroller , wizards things of beauty, elegance , simplicity. have joyfully thrown away 3 months of work on wizards in webforms convert them new mini wizard framework. bad.