@afilev: "I am not familiar with java web applications but I believe this is what
STRUTS does.
ASP.Net is a strange beast. It simplifies the web development by assuming
that every
page post back to itself only and every ASP.NET page has one FORM only.
In my opinion this assumption defeats the reason of having a switch board
module to handle all the requests.
On the other hand such a module would be almost a  must otherwise. I've seen
a Java Servlet application which was a complete mess
and one of the reason is that there was no notion of  centralized controller
(switch board)  to handle and dispatch different requests.
I read the VSJ article and also think that developing such a module to
handle calls to a ASP.NET pages is pointless if one wants to
use rich event model of ASP.NET model.
Even thou  in theory this will make aspx page more easy to decouple from a
module,  the extra effort probably wont be worthed.
Angel "
    @afilev: "Sorry.  Hit the wrong button.
Previous message should be a response to
the Peter's  post few items before."
    @scottroberts: "I agree with most of your post. However, it is still possible to have a
front-controller (or switch board) in ASP.NET.
I view the post-back as simply a way to transfer control back to the server.
Once control is at the server I can do whatever I want. For example, a
button on an ASP.NET form might do this:
private void Login_Click(object sender, System.EventArgs e)
{
    Requests.LoginRequest loginRequest = new LoginRequest();
    loginRequest.Username = Username.Text;
    loginRequest.Password = Password.Text;
    Requests.Controller.ProcessRequest(loginRequest,HttpContext.Current);
}
In this case, the class "Requests.Controller" is responsible for both
executing the Request object (loginRequest) and possibly transferring
control somewhere else based on the results of processing the Request object
(maybe to the user's home page). You could do this any number of ways,
including "Context.Server.Transfer()", "Context.Response.Redirect()", etc.
So, while control doesn't go directly from the client browser to the
controller, with a little care on your part you can still achieve the same
results.
It will be interesting in 10 years to see how much business logic is coded
directly into "code-behind" modules of aspx pages. My bet: A lot.
news:<email_address>
<quote>
seen
controller"
{'source': 'USENET', 'other_information': '{"reply_count": 2, "forum_name": "borland.public.delphi.oodesign.20141024.mbox"}', 'file': 'data/output/usenet-borland.public.parquet'}