Glad to see you worked it out...
ok everything is cool, the articles tell what i thought in the first place.
i found my problem
using response.flush inside the code actually cancels the caching.
how should i know about it?
i don't think anywhere this is told.
i had to put and remove all kinds of functions in my code in order to trace
this.
is this a must?
who knows......
z,
Could you read these articles,
and then come back with any questions you might still have ?
http://msdn.microsoft.com/library/d...pp/html/aspnet-cachingtechniquesbestpract.asp
http://msdn.microsoft.com/asp.net/c...=/library/en-us/dnaspnet/html/asp03282002.asp
From this last article :
VaryByParam: This attribute allows us to control how many cached
versions of the page should be created based on name/value pairs
sent through HTTP POST/GET.
The default value is None.
None implies that only one version of the page is added to the Cache,
and all HTTP GET/POST parameters are simply ignored.
The opposite of the None value is *.
The asterisk implies that all name/value pairs passed in are to be used
to create cached versions of the page.
The granularity can be controlled, however, by naming parameters
(multiple parameter names are separated using semi-colons).
i'm trying to understand you
if i have a categoryID parameter for my page.
and i have VaryByParam=none i should get the first cached snapshot of the
page what ever parameter is sent after the page being cached.
at least that's what i thought.
so what is happening with this page when it gets 2 different requests, it
gives fresh data?
what you mean i your last line (i quote
A VaryByParam of "none", won't *cache* by parameters,
but the *data returned* will, still, vary by parameters
so VaryByParam of "none" won't cache the page at all and gives fresh
data?
another question:
if i put a response.write of the timestamp in my page_load
of a chached page,
shouldn't the value not change between cached requests?
my method should not execute if the output is being cached, so why does it
execute?
TIA, z.
z.,
When you make requests with different parameters,
you *should* get different data returned.
That's the *purpose* of parameters, to enable dynamic data
to be returned depending on the parameter sent.
If you set VaryByParam to "none", all that means
is that the *caching* won't vary by parameters.
The *data* will, still, vary by parameters.
A VaryByParam of "categoryID" would create separate
*cache entries* for every categoryID in a catalog, for example.
A VaryByParam of "none", won't *cache* by parameters,
but the *data returned* will, still, vary by parameters.
sorry about the previous post, by mistake not completed.
i have an asp.net page with the line
<%@ OutputCache Duration="30" VaryByParam="none" %>
but when i make requests to the page with different parameters, i get
different result,
but i tries to check if i set the VaryByParam to none there should be
the
same output for different parameters, so why does it not work?
TIA, z.
