*sticks hands in pocket*
Well I dunnos.
I was just wondering what it was. And no, if its an HTML page it doesn't have that
problem.
I thought maybe since its all being built dynamically and the pages are called
dynamically via URL variables,
the browser might always pick it up as a 'new' page.
Yes the images are cached beforehand with Javascript.
*sulks*
*shuffles off*
-Gel
-----Original Message-----
From: Philip Arnold - ASP [mailto:[EMAIL PROTECTED]]
> Hawos all,if a website uses something like a single template,
> default.cfm to call several other pages wich CFINCLUDEs...does
> this prevent the browser from using cached images to load the page?
>
> I just think that the browser keeps pulling the images from the
> net, instead of using them from its cache, since the text of
> the page comes up really quickly (pulled from a database) but the
> images always take a long time to eventually pop into
> place, whereas if it were all coming from Cache I would have
> expected them to just display almost instantly?
>
> Anyone run into this issue? Is it even an issue at all ? ^_^
Come on Gel - how can whether you use a CFInclude effect whether the browser
pulls an image from cache or from the server? The CF template builds the
whole thing and then sends it down to the browser (unless you use CFFlush) -
the browser only sees HTML...
What you should do is check the images are pre-loaded in JS (and use the
variables rather than the image names) also check the browser setting isn't
"Check for New Versions of Stored Pages" to Never
Copy the page as a HTML document and see if you get the same issue - I bet
you will
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
