Hockey wrote:POSTBACK is not a feature exclusive to ASP.NET, PRADO implements a POSTBACK mechanism as well.
That's because PRADO is trying to be .NET
Hockey wrote:Really, it just avoids having to re-POST data when a FORM doesn't validate, how you implement doesn't really matter IMHO.
From my understanding POSTBACK has nothing to do with avoiding reposting form data. Postbacks can be used for all sorts of things in which you want to know if the page that was posted happens to be the same page you are on after the page (in .NET the entire page is one big form) was posted. I know from some of my tests that POSTBACK can maintain state from the original post page as well as state from the new post page.
Hockey wrote:I am now more curious as to what kind of information or purpose a REQUEST object holds. Until now I haven't been able to justify adding an object called request, to simply wrap super globals such as GPC.
Remember the request and response objects from ASP.old (VBScript). Yeah, the request object could be something like that.
Hockey wrote:Any examples or detailed reasons for using REQUEST?
If you happen to touch REQUEST data more than once, and you are building an OOP application, it makes sense to put the REQUEST specific data into request object, much like it makes sense to put the RESPONSE type stuff into a RESPONSE object. No?