R
ruca
Hi
Can I pass a DataSet from one page (parent) to another (child, popup
window)?
How can I do that?
Can I pass a DataSet from one page (parent) to another (child, popup
window)?
How can I do that?
R
Raymond Lewallen
Ruca,
Look at the System.Web.Caching namespace. This link should help.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/
frlrfSystemWebCaching.asp
HTH,
Raymond Lewallen
Look at the System.Web.Caching namespace. This link should help.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/
frlrfSystemWebCaching.asp
HTH,
Raymond Lewallen
C
Cor
Hi Raymond,
Are you sure of this, as far as I know is the caching namespace to share
frequently used data for all your clients. Let say by instance an article
list you loads one time a day and all pages from all clients can use that.
For sharing data between pages from one client is still the Session in my
opinion.
However maybe I am wrong in this?
Cor
Are you sure of this, as far as I know is the caching namespace to share
frequently used data for all your clients. Let say by instance an article
list you loads one time a day and all pages from all clients can use that.
For sharing data between pages from one client is still the Session in my
opinion.
However maybe I am wrong in this?
Cor
R
Raymond Lewallen
Cor,
I use a unique key name to identify the item in the system cache, usually
based on our unique applicationID or a sessionID combined with "DataSet" to
create a unique name. We have problems with sessions being lost in our
application and timeout errors connecting to our Sql Server SessionState
database, so caching is a better option for us.
Ruca,
Cor is correct. If this a dataset that is common data for all users of your
application, you definately should be using the System.Web.Caching.
However, if the data is unique to each client accessing your application,
you can use sessionstate. I still use caching instead of session state due
to session problems we have. I use a unique key name to identify the
dataset for the unique client.
Check both caching and sessions and see which options will work the best for
you. Chances are you will end up using both solutions somewhere along the
way.
HTH,
Raymond Lewallen
I use a unique key name to identify the item in the system cache, usually
based on our unique applicationID or a sessionID combined with "DataSet" to
create a unique name. We have problems with sessions being lost in our
application and timeout errors connecting to our Sql Server SessionState
database, so caching is a better option for us.
Ruca,
Cor is correct. If this a dataset that is common data for all users of your
application, you definately should be using the System.Web.Caching.
However, if the data is unique to each client accessing your application,
you can use sessionstate. I still use caching instead of session state due
to session problems we have. I use a unique key name to identify the
dataset for the unique client.
Check both caching and sessions and see which options will work the best for
you. Chances are you will end up using both solutions somewhere along the
way.
HTH,
Raymond Lewallen