Might I suggest you take a look at book by WROX titled
ASP.NET Website Programing Problem - Design - Solution
Visual Basic .net Edition
The ISBN is 1-86100-816-3
This book offers some design patterns for each tier of a 3
tier business application. The DB layer patterns have
been very useful to me and echo what Chris has posted in
regards to keeping the connection open to the DB for as
little time as possible.
-----Original Message-----
I have a question regarding the design of asp.net websites. If I'm followinga reasonably object oriented approach to designing my sites, and have a dataaccess class, business logic classes and then the display code (the actualpages), what would be the best way to handle my database connections?
Lets say I have a page that has three main dynamic areas that are constantlyupdated and therefore not well suited to being cached, would it be best tohave one connection object that is opened on the page and then passed to thethree controls, or would it be best to have them completely seld contained,opening and closing their own connections?
In traditional ASP I would have had one connection opened at the start ofthe page and then closed at the end, with all classes and includes withdatabase access expecting there to be an open connection. Obviously thearchitecture in .Net web applications is different, and I was wondering ifanyone could give me some advice on what's the best/most efficient way ofdoing something liek this in .Net.
Thanks in advance for any advice,
Tim.
.
