Cache an object

[Prashanth]

Hi,
I want to cache an object whose scope in only within the page. The
cache should expire once the user leaves the page. How can I do it?
Regards,
Prashanth

[sloan]

The 3 main ways to cache objects are:

Application
Session
Context

http://msdn2.microsoft.com/en-us/lib...e.context.aspx

Context gives you a "one time shot" at getting the values.

It may not be exactly what you looking for, however, those are the main 3,
and Context is the closest one to your description.
If you look at my blog:

You can use my Session Object Wrapper, and my .Remove method.

http://sholliday.spaces.msn.com/PersonalSpace.aspx 10/24/2005 entry

"Prashanth" <pr****@gmail.com> wrote in message
news:11**********************@r2g2000cwb.googlegro ups.com...

Hi,
I want to cache an object whose scope in only within the page. The
cache should expire once the user leaves the page. How can I do it?
Regards,
Prashanth

[Karl Seguin [MVP]]

Sloan:
You are missing the viewstate. I only mention it because it might be what's
wanted in this case. "scope of the page" isn't particularly clear though, so
it's hard to tell. Context is ideal for dealing with the start of page
processing (say init) to the end (say prerender). If you want the data to
survive a postback, you'll need to do something more persistant. ViewState
might work, but it's rendered on the client so it needs to (1) be
serializable and (2) be small.

Karl

--
http://www.openmymind.net/
http://www.fuelindustries.com/
"sloan" <sl***@ipass.net> wrote in message
news:e2**************@TK2MSFTNGP02.phx.gbl...

The 3 main ways to cache objects are:

Application
Session
Context

http://msdn2.microsoft.com/en-us/lib...e.context.aspx

Context gives you a "one time shot" at getting the values.

It may not be exactly what you looking for, however, those are the main 3,
and Context is the closest one to your description.
If you look at my blog:

You can use my Session Object Wrapper, and my .Remove method.

http://sholliday.spaces.msn.com/PersonalSpace.aspx 10/24/2005 entry

"Prashanth" <pr****@gmail.com> wrote in message
news:11**********************@r2g2000cwb.googlegro ups.com...

Hi,
I want to cache an object whose scope in only within the page. The
cache should expire once the user leaves the page. How can I do it?
Regards,
Prashanth

[sloan]

Ooooops!

You're right Karl... I forgot about that one!

That's why I should answer posts that early in the morning.


"Karl Seguin [MVP]" <karl REMOVE @ REMOVE openmymind REMOVEMETOO . ANDME
net> wrote in message news:e3**************@TK2MSFTNGP02.phx.gbl...

Sloan:
You are missing the viewstate. I only mention it because it might be what's wanted in this case. "scope of the page" isn't particularly clear though, so it's hard to tell. Context is ideal for dealing with the start of page
processing (say init) to the end (say prerender). If you want the data to
survive a postback, you'll need to do something more persistant. ViewState
might work, but it's rendered on the client so it needs to (1) be
serializable and (2) be small.

Karl

--
http://www.openmymind.net/
http://www.fuelindustries.com/
"sloan" <sl***@ipass.net> wrote in message
news:e2**************@TK2MSFTNGP02.phx.gbl...

The 3 main ways to cache objects are:

Application
Session
Context

http://msdn2.microsoft.com/en-us/lib...e.context.aspx

Context gives you a "one time shot" at getting the values.

It may not be exactly what you looking for, however, those are the main 3, and Context is the closest one to your description.
If you look at my blog:

You can use my Session Object Wrapper, and my .Remove method.

http://sholliday.spaces.msn.com/PersonalSpace.aspx 10/24/2005 entry

"Prashanth" <pr****@gmail.com> wrote in message
news:11**********************@r2g2000cwb.googlegro ups.com...

Hi,
I want to cache an object whose scope in only within the page. The
cache should expire once the user leaves the page. How can I do it?
Regards,
Prashanth

[Prashanth]

Karl,
I want the data to survive a post back but cannot use viewstate since
the objects is not serializable.

Karl Seguin [MVP] wrote:

Sloan:
You are missing the viewstate. I only mention it because it might be what's
wanted in this case. "scope of the page" isn't particularly clear though, so
it's hard to tell. Context is ideal for dealing with the start of page
processing (say init) to the end (say prerender). If you want the data to
survive a postback, you'll need to do something more persistant. ViewState
might work, but it's rendered on the client so it needs to (1) be
serializable and (2) be small.

Karl

--
http://www.openmymind.net/
http://www.fuelindustries.com/
"sloan" <sl***@ipass.net> wrote in message
news:e2**************@TK2MSFTNGP02.phx.gbl...

The 3 main ways to cache objects are:

Application
Session
Context

http://msdn2.microsoft.com/en-us/lib...e.context.aspx

Context gives you a "one time shot" at getting the values.

It may not be exactly what you looking for, however, those are the main 3,
and Context is the closest one to your description.
If you look at my blog:

You can use my Session Object Wrapper, and my .Remove method.

http://sholliday.spaces.msn.com/PersonalSpace.aspx 10/24/2005 entry

"Prashanth" <pr****@gmail.com> wrote in message
news:11**********************@r2g2000cwb.googlegro ups.com...

Hi,
I want to cache an object whose scope in only within the page. The
cache should expire once the user leaves the page. How can I do it?
Regards,
Prashanth

[Karl Seguin [MVP]]

Well, either make it serializable(which isn't always possible) or you'll
need to persist it in memory. You are likely stuck using sessions.

Karl

--
http://www.openmymind.net/
http://www.fuelindustries.com/
"Prashanth" <pr****@gmail.com> wrote in message
news:11**********************@b68g2000cwa.googlegr oups.com...

Karl,
I want the data to survive a post back but cannot use viewstate since
the objects is not serializable.

Karl Seguin [MVP] wrote:

Sloan:
You are missing the viewstate. I only mention it because it might be
what's
wanted in this case. "scope of the page" isn't particularly clear though,
so
it's hard to tell. Context is ideal for dealing with the start of page
processing (say init) to the end (say prerender). If you want the data
to
survive a postback, you'll need to do something more persistant.
ViewState
might work, but it's rendered on the client so it needs to (1) be
serializable and (2) be small.

Karl

--
http://www.openmymind.net/
http://www.fuelindustries.com/
"sloan" <sl***@ipass.net> wrote in message
news:e2**************@TK2MSFTNGP02.phx.gbl...

>
> The 3 main ways to cache objects are:
>
> Application
> Session
> Context
>
> http://msdn2.microsoft.com/en-us/lib...e.context.aspx
>
> Context gives you a "one time shot" at getting the values.
>
> It may not be exactly what you looking for, however, those are the main
> 3,
> and Context is the closest one to your description.
>
>
> If you look at my blog:
>
> You can use my Session Object Wrapper, and my .Remove method.
>
> http://sholliday.spaces.msn.com/PersonalSpace.aspx 10/24/2005 entry
>
>
>
> "Prashanth" <pr****@gmail.com> wrote in message
> news:11**********************@r2g2000cwb.googlegro ups.com...
>> Hi,
>> I want to cache an object whose scope in only within the page. The
>> cache should expire once the user leaves the page. How can I do it?
>> Regards,
>> Prashanth
>>
>
>