That may depend on the complexity of the business logic involved!!!
And also the gui complexity and differences between the types of 'Requests'.
If the gui & business logic is simple enough, using one page would be my
preferred option.
On the otherhand, if the gui & business logic requirements cause my code to
become long and complicated,
i tend to break it down & implement some sort of separation (ie: different
files)
This could just be a matter of preference though!
Cheers,
Adam
"Raul Macias" <ra*********@hotmail.com> wrote in message
news:eG**************@TK2MSFTNGP15.phx.gbl...
From the developer standpoint it would be better to have just one page and
filter the information that the user wanna see. Is much better to mantain
one page instead of three.
"Trex" <ra**********@hotmail.com> wrote in message
news:Eo*****************@newsread3.news.atl.earthl ink.net... My question is on the design of a web app...let's say I was tracking
requests for something and I wanted my web app to show information about
the different requests in the system. A list of pending requests,
approved requests, completed, etc & so on. Do most asp.net developers
create a page for each request?
pendingRequests.aspx
approvedRequests.aspx
CompletedRequests.aspx
etc.
Or
Request.aspx?type=1
Request.aspx?type=2
Request.aspx?type=3
what decisions are you making to decide which direction you go?
Regards,
Trex
