[Mono-list] Logic/Reason to ASPX caching ?????

A Rafael D Teixeira rafael.teixeirabr@terra.com.br
Thu, 17 Jun 2004 10:07:45 -0300


On Tue, 2004-06-15 at 13:21, ted leslie wrote:
> Anyone know what the story is on the caching of ASPX files,
> what i mean is,
> I change code in a ASPX file and re-run the page, and I may/or may not 
> get the change,
You always get the changes when changing the page, directives-driven
caching is limited to the output and dependent on the source page, and
can be made dependent on other conditions

> I can reset the mono service, and it will allways refresh, but you don't 
> always have to do this.

You never should have to reset the service, just "touch" a dependency,
like Web.Config, then XSP will restart the ASP.NET application affected
(and no other).

>  From a hosting-company point of view, it would be important not to have 
> to restart server to get a ASPX page to refresh,
> anyone know what the scoop is here?

As I said the only chance caching would make a page not to refresh is if
you explicitly (by code) cache a page or parts of it without any
dependencies and without a timeout. That is just bad application design
not something inherent to ASP.NET caching, so bill your client the time
your team will need to debug the client app and correct it's caching

> -tl

Hope it Helps,
Rafael "Monoman" Teixeira 
Mono Hacker since 16 Jul 2001 - http://www.go-mono.org/
Mono Brasil Founding Member - http://monobrasil.redesolbrasil.org/
English Blog: http://monoblog.blogspot.com/
Brazilian Portuguese Blog: http://monoblog.weblogger.terra.com.br/