Mr kleiner dan groter dan teken can der Valk een verrassing voor kleiner
dan groter dan in de keten om te reageren zeg antwoord op het bericht zeg
je bericht
Verzonden door spraakgestuurd bericht! www.drivemode.com


Op wo 14 dec. 2016 20:07 schreef Sascha Nemecek <[email protected]>:

> Hi Michael,
>
>
> Am 2016-12-14 um 05:30 schrieb Michael A. Patton:
> > I've been trying to debug a new set of code in a file referenced with
> > <use/>.  As far as I can determine, the only way to get the server to
> > load the new file is to use the "Flush all caches" button in the admin
> > interface.
>
> I have had similar experiences with the <use/> tag and can therefore
> confirm your observation.
>
>
> > This seems like rather a big hammer, it affects all the
> > sites on the server, not just the one I'm working on. Is there
> > something lighter that I could be using?
>
> Docs[1] for <use/> indicate that it caches the results quite heavily and
> mentions the attribute nocache='1'. Might be worth a try.
>
>
> > One reason I'm worried about that is I have some pages with lots of
> > business graphics images (e.g. http://MAP.MAP-NE.com/Mail/stats.html).
> > Those go in the cache, right?  If at about the same time as I flush the
> > cache someone is loading such a page, it seems like they may end up
> > getting some broken images that got flushed out of the cache after they
> > were generated in the server parse of the file and before the browser
> > loads the referenced image.
>
> Don't know if this could really happen. I would assume there is some
> kind of locking mechanism that prevents such situations.
>
>
> > There are also a lot of <cimg/> generated images, they have this problem
> > as well, I suspect. If you want to see lots of those, they are in the
> > photo gallery on that same site.
>
> According to the <cimg/> docs[2] you can set a timeout.
>
>
> Cheers,
> Sascha
>
> [1] http://docs.roxen.com/roxen/6.1/web_developer_manual/variable/use.tag
> [2] http://docs.roxen.com/roxen/6.1/web_developer_manual/graphics/cimg.tag
>
>

Reply via email to