Search results matching tag 'Cache'

Re: How to set Page output caching for some expiry date

naveen_j80 — Wed, 16 Dec 2009 05:00:00 GMT

Hi Hua,

I know that VaryByParams["none"] = true will apply the same cache for all query strings. My requirement is, my report will change based on the parameters in the URL. So that, it will cache data based on URL that most frequently used by the users.

Below is sample web application i have created and i observed same issue with it, please have a look

Default.ASPX

Default.ASPX.CS

protected void Page_Load(object sender, EventArgs e)
{
    Response.Cache.SetExpires(DateTime.Now.AddDays(3));
    Response.Cache.SetCacheability(HttpCacheability.Server);
    Response.Cache.SetValidUntilExpires(true);
    Response.Cache.VaryByParams["*"] = true;

    id.Text = DateTime.Now.ToString();
    if (Request.QueryString["a"] != null)
    {
        Response.Write(Request.QueryString["a"].ToString());
    }
}

If we build this solution and browse as shown below

URL: http://localhost/WEBSITE1/Default.aspx, Result: 12/16/2009 10:56:40 AM

URL: http://localhost/WEBSITE1/Default.aspx?a=10, Result: 10, 12/16/2009 10:59:40 AM

This is the expected behavior and working fine. But issue here is, it is caching this data only for 1hr or so. Not till the time we specified in the SetExpires method.

How to set Page output caching for some expiry date

naveen_j80 — Fri, 11 Dec 2009 05:00:00 GMT

Hi,

I am using Page purout cachine in my asp.net web application. I have implemented page output cachine to cache pages at server for 3 days by using the below code

Response.Cache.SetExpires(DateTime.Parse("12/7/2009 11:55:00 PM")); // Consider some feature date more than 3 days.
        Response.Cache.SetCacheability(HttpCacheability.Public);
        Response.Cache.SetValidUntilExpires(true);
        Response.Cache.VaryByParams["*"] = true;

When i request my page first time it is taking some time to return results to the browser and the subsequent requests for the same page is served from the cache and it is fast. But when i request same page after 3 or 4 hours, instead of serving page from server cache it is starting processing the whole page lifecylce (executing stored procedutes, binding data to gridview, etc..).

The above code should cache the page for some days but it is not doing that. Is there any issue with the above code?

My requirement is, i need to keep some pages in cache for 3-7 days. My requirement is, i have reports which takes long time to generate and refreshes weekly once.

Thanks in advance...

Re: How to set Page output caching for some expiry date

naveen_j80 — Fri, 11 Dec 2009 05:00:00 GMT

Hi Suresh,

Thanks for your information. I have done same thing but the requested page is cached for 1hr (or so) not till I specified in the SetExpires(...) method.

Re: slow first page

hobeau43 — Fri, 04 Dec 2009 05:00:00 GMT

ASP.net applications can be built in 2 ways. The first is an ASP.net website the second is an ASP.net Web Application. ASP.net websites have to be compiled on the fly and save the compilation in what is called the Output Cache which explains why the first page always takes much longer than the preceding pages. The first page that is requested causes the ASP.net Website to compile and it is held in the output cache for a limited duration. For more information on this and how to control caching checkout http://msdn.microsoft.com/en-us/library/aa478965.aspx . An ASP.net web Application, on the other hand, is a precompiled web application. That is, it is compiled into a DLL and doesn't require a recompile every time a page is requested. Another benefit of ASP.net web applications is the fact that the code is debugged (from a compiler standpoint) as it is all precompiled before uploading it to the production server. The con of using an asp.net web application is the fact that if you want to just quickly make a small change it is a bit more difficult as the entire application must be recompiled and uploaded. So it basically comes down to how you want your development model to be.

Equivalent of Page_Init in web forms for MVC

ydesai — Fri, 20 Nov 2009 05:00:00 GMT

Hi folks,

I have an ASP.NET MVC web app setup and I need to know what the equivalent of page_init is for ASP.NET? I need to set the application to not cache anywhere. Is the global.asax the best place for this? If so, which event?

Basically, I need to put it so that everytime there is a postback, that event must be called. I am trying to turn off caching at all levels as this is a blackberry mobile app.

Code to add:

Response.Cache.SetExpires(DateTime.UtcNow.AddMinutes(-1);
Response.Cache.SetCacheability(HttpCacheability.NoCache);
Response.Cache.SetNoServerCaching();
Response.Cache.SetNoStore();

thanks.

The local copy of this webpage is out of date, and the website requires that you download it again

bapanpally — Wed, 18 Nov 2009 05:00:00 GMT

hi people,

plzz help me its very urgent,

to disable the cache from client and on server side i added these lines of code, and it works fine in every broswer.

my main concern is, i have a address page(when ever i visit this page it loads the page with info that is there in the database) it has a dropdown for states and textbox for zipcode, when a user enters a wrong zipcode for that state it does the server side validation and displays a serverside error message that "you entered a wrong zipcode", after this if i enter the correct zipcode click save button it saves successfully and takes me to next page, (i can see the new data in the database table)

my problem comes here,

scenario1:(first time page loads and if i enter correct zipcode(i mean here im not entering the wrong zipcode) and click on save button) it takes me to another page, if i click on browser back it displays with the new data what is there in the database i mean page loads(it goes through pageload event and populates all the fields)

scenario2:

if i enter wrong zipcode it gives serverside error message, after i correct it and enter the correct zipcode and click on save button it takes me to the next page,

my problem comes here,

when i hit the browser back button instead of loading the page with the data in the database it says "webpage is expired". if i do the refresh then it reloads the page with new data.

plzzzz help me guys, i need to fix it in production...... i'm not a guru in asp.net, still i'm in learning process .....

onemorething i tried every HTTP headers

'Dim kj As String = "private, no-cache, must-revalidate"

'Response.AddHeader("Pragma", "no-cache")

'Response.AddHeader("cache-control", kj)

Response.Cache.SetNoStore()

i hope gud people out there helps me

plzzz reply if u have a clear answer and how to do it, remember it should wrk in all browsers

Caching MVC Routes Using IIS 7

kengineer — Mon, 16 Nov 2009 05:00:00 GMT

We're trying to add caching to our MVC application using the IIS 7 Caching Module. However, the problem that we're running into is that the IIS 7 Caching module asks that you provide a file extension when you register a new cache rule. Since this is MVC, there is not file extension, just routes. Does anyone know if it is possible to use IIS 7 caching for MVC? We realize we can use the caching features built into Asp.Net, but we curently would prefer to control the caching at the web server.

Manage users online on social networking

Jim77 — Wed, 11 Nov 2009 05:00:00 GMT

I want to build a social networking.

I read in several places using Session to manage users online is not an effective way.

My question is what is the most efficient way to register users.

Session or Cache?

If using Cache, what is the best way to implement it?

I want to build a social networking.
I read in several places that using Session to manage users online is not an effective way. Particularly for mid large proportions growing network.
My question is what is the most efficient way to register users.
Session or Cache?
If using Cache, what is the best (and custom) way to implement it?

ObjectDataSource Caching

dhavalshah — Mon, 09 Nov 2009 05:00:00 GMT

Can u help me understand following statement's meaning...

"The ObjectDataSource control allows you to cache all types of data, but you should not cache objects that retain resources or state that cannot be shared to service multiple requests (for example, an open SqlDataReader object), because the same instance of the object will be used to service multiple requests."

i m totally confused with abt statement..!!!!

Options in caching

Agust — Sat, 07 Nov 2009 05:00:00 GMT

Hi guy's

I am considering my options - any input welcome! Here is the situation:

1. A rather complicated database - several queries are heavy joins.

2. I have several web forms. They do not have huge traffic - for the sake of discussion let's say our goal is to have them cope well and speedy with 10 users simultaneously.

3. In some cases I have done some t-sql tricks to materialize views and thus speed up heavy queries. Now - I want to move away from that - less stuff in t-sql but more stuff in my new .NET application layer.

4. Now - I have done page level caching (directive at the top) - and cached UserControls - it works - but the problem is that when the cache needs to be updated... well then the page is slow! And my goal is that my users do not experience that at all. So, I would like to find a away to have a background process update the cache so the pages do not have to.

5. So, all this to now share my idea:

The asp.net cache object is great - I have used it several times. What if I create an asp.net page (le't call it updateCache.aspx) which will take care of updating any data that I want to keep in the cache. Then, I will have a scheduled task (which can run anywhere) and call my updateCache.aspx page at an interval of my choice - the page will go through my cached objects (I can wrap them in classes who will each now when they want to be updated) - and refresh any objects that want to be refresh.

Now - when my (normal) web forms are serving my users - they will not need do any heavy data loading but simply fetch from the cache.

So - what do you guy's think? Am I making this to complicated? Is there another more plain way to accomplish this? Again - my main goal is that my users never need to way for slow queries, and I do not want to use sql server to do the caching - I want to do the caching in my C# code.

I'd appreciate any input - Agust - Iceland