ASP architecture

[DwC]

Hey All,

I am fairly new to ASP and web apps and am having trouble working out
the architecture for the app we are currently working on. It allows a
user to log in and have access to pages that wouldn't be available
publicly. We also need to check the user id each time data is accessed
from the db as users will only have access to their own records.

We are from a background of windows forms applications where the
standard architecture would be to have a controller that is in charge of
the window being displayed on the screen and one/many database classes
that interact with the db, controlled from the controller.

Is the architecture that is used by a web app simply to create a new
database access object each time the page is loaded and then open and
close the connection after each request, then store log in information
in a session variable with say the user type, user id, name etc. Then
each time we request data we send the user type or id to the db class
and it determines what is to be returned?

Can anyone help with just some general information on how this type of
web application would be structured, or some good sources of information
on web application architectures?

Thanks in Advance

Daniel

[garethdjames]

Would you appreciate any freelance consultation?

[DwC]

ga**********@gmail.com wrote:

Would you appreciate any freelance consultation?

Free consultation would be nice.

Just looking for something to move us in the right direction.

Thanks

[Eliyahu Goldin]

A classic document:

Building Secure ASP .NET Applications .pdf Download
http://www.microsoft.com/downloads/d...C-BF9C6593F25E

Eliyahu

"DwC" <em***@email.com> wrote in message
news:gN****************@nnrp1.ozemail.com.au...

Hey All,

I am fairly new to ASP and web apps and am having trouble working out
the architecture for the app we are currently working on. It allows a
user to log in and have access to pages that wouldn't be available
publicly. We also need to check the user id each time data is accessed
from the db as users will only have access to their own records.

We are from a background of windows forms applications where the
standard architecture would be to have a controller that is in charge of
the window being displayed on the screen and one/many database classes
that interact with the db, controlled from the controller.

Is the architecture that is used by a web app simply to create a new
database access object each time the page is loaded and then open and
close the connection after each request, then store log in information
in a session variable with say the user type, user id, name etc. Then
each time we request data we send the user type or id to the db class
and it determines what is to be returned?

Can anyone help with just some general information on how this type of
web application would be structured, or some good sources of information
on web application architectures?

Thanks in Advance

Daniel