DataSet Caching
Messages   Related Types
This message was discovered on ASPFriends.com 'aspngbeta' list.


Unico Hommes
-- This message, which was originally sent to "aspng", has been moved to "aspngbeta" mailing list by the List Master --

Three questions:

1) Do my .asmx and .aspx programs share the same Session and Application
scope ?

2) Is it a generally a good idea to store DataSet objects at Application
scope assuming they do not get too large ? How do I determine how much
memory it takes up ?

3) With Connection Pooling, can/should I call Connection.Close() ?

Thanx,

Unico

Reply to this message...
 
    
Scott Swigart
1. Yes, your .asmx and .aspx pages share the same Session and Applicaiton
scope.

2. It would be better to store a DataSet in a Cache object rather than
Application. If you store it in Application, always in memory, even if
memory gets scarce, and even if it doesn't get hit for a long time. If you
store it in Cache, then it can get dropped if it sits idle for too long, or
memory gets scarce. The only additional burden is that you need to make
sure it's still in cache.

If Cache("MyDataSet") is Nothing then
ds = BuildDataSet()
Cache("MyDataSet") = ds
Else
ds = CType(Cache("MyDataSet"),DataSet)
End if

Hope this helps.

Scott Swigart
3 Leaf Solutions, LLC
Click here to reveal e-mail address
www.3leafsolutions.com

"Unico Hommes" <Click here to reveal e-mail address> wrote in message news:379179@aspngbeta...
[Original message clipped]

Reply to this message...
 
 
System.Data.DataSet




Ad
MBR BootFX
Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT
 
 Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd.
Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com