Re: ASP.Net Newbie Questions
From: Natan (nvivo_at_mandic.com.br)
Date: 11/27/04
- Next message: BG: "More Strange Debugger Antics"
- Previous message: charlie: "Best practice"
- In reply to: MDW: "Re: ASP.Net Newbie Questions"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 27 Nov 2004 18:27:43 -0200
MDW wrote:
> I'm a bit unclear as to what you mean by "client-side events on the server".
> When I hear client-side, I think of JavaScript and stuff like form
> validation. Is ASP.Net trying to pre-empt the kind of things that JavaScript
> does? There does seem to be quite a bit of architecture in place that could
> be used to validate user input. Is that the whole purpose of the PostBack
> entity?
See, you must understand how a page in asp.net works first. First, the
ViewState...
ViewState is actually a serialized hidden field in a <form
runat='server'> that asp.net manages automatically for you. all the data
on every <control runat="server"> you put in a form are stored in that
field.
Now, when the guy said "client-side event on the server", that means the
action happened in the client, but when you posted the page, the server
does something, not the client. This works because asp.net manages the
viewstate storing how the fields look before rendering the page, and
comparing with how they look after you submit a page.
Because GET is not good for sending lots data (viewstate can become big
depending on what you store in it), then the default is POST. So you
have "postback". You post the page, asp.net detects what happened
comparing data and checking fields you sent, and fires the events.
Yes, it ends sending and receiving more data then you would need, but
the benefits are bigger... and data compressing should take care of most
problems.
It's not trying to "replace javascript". It's just a way to control what
asp.net must do.
> Also, if the philosophy of ASP.Net is not to have everything on one page,
> does that mean that Request.Form still exists? Can I still put
> "action=nextpage.aspx" on a form to have that form post its data to another
> page?
Yes. Actually you can program exactly like you did in old ASP. But you
will figure out that it sucks because you have much better ways to do
things in asp.net.
Of course in some cases you still need to do some Request.QueryString...
but only when you need to pass date to other page. As you can do most
of the job in the same page, you will use it, but not as much as you
used to.
> As I've said, the book I'm using seems to be pretty sub-par. I can't find
> the answers in there, and all the examples I can find use single pages -
> there is no "how to post a form to another page" example. I apologize if
> these are ridiculously stupid questions.
UNfortunately, you cant. ASP.NET automatically modify any "<form
runat="server"> to post to itself. You can post to other page if you
don't use "runat="server"".. but then you don't have many features
asp.net gives you.
Sometimes i miss this too. But in many cases you will see there are
better ways to do somethings. Try to understand how it should be done,
and why instead of trying to do things the old way. I think it will be
better this way.
btw, sorry for my english.. =)
[]'s
- Next message: BG: "More Strange Debugger Antics"
- Previous message: charlie: "Best practice"
- In reply to: MDW: "Re: ASP.Net Newbie Questions"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
