|
|
|
|
|
| | |
| |
Active Server Pages ASP ASP.NET .aspx .ascx Web HTML Developer Internet Microsoft Web Services Visual Studio .NET CJWSoft ASPProtect ASPBanner ASPClassifieds
(Advanced)
(Components)
(Database)
(General)
(Vbscript)
|
|
|
|
Subject: |
Connection Pooling / Connection and Recordset Objs. |
|
From: |
shao |
|
Date: |
3/18/1999 3:46:20 PM |
|
IP: |
160.254.115.80 |
I read some article saying that in order to take advantage of connection pooling, better create and destroy connection object on a per-page basis. So assume we have an .asp file. In the beginning of the asp file, I create the objects. In the end, I close the objects and set them to Nothing. This makes sense so far. But what happens if in the middle of the asp file, I have a response.redirect statement. This means the "close" and "=nothing" statements in the end won't get executed because it never reaches the end. should I add "close" and "=nothing" before every ".redirect" statement? Or it will takes care of it itself because it goes out of scope of page? What's the right way to handle this?
Thanks. |
Follow Up - Re: Connection Pooling / Connection and Recordset Objs. - Chad Brooks 3/19/1999 2:33:05 PM
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
