On Aug 10, 11:26 am, "Derek Westfall" <[EMAIL PROTECTED]> wrote: > I believe that using the nifty functions like request.inhead.swfObject=1 > runs afoul of the objectbroker webskin cache. > > Specifically, the content put in the HEAD by _farcryOnRequestEnd.cfm is not > cached. > > So imagine a page that: > 1) has an ad rule that sets request.inhead.swfObject=1 > 2) uses a webskin that is cached in the objectbroker > > The first time I visit the page everything is great and my flash objects > show up because swfObject.js is put in the head. > The next time I visit the (now cached) page -- no flash, because swfObject > is not in the head. > > Can someone confirm this? Can objectbroker be modified to cache what > _farcryOnRequestEnd adds via cfhtmlhead?
What version of core are you running? Although what you are experiencing may be a bug, the *inhead* feature is specifically designed to cache inhead directives right along with the webskin cache to prevent exactly these sorts of things from happening. So when a page is composited from cache it should understand all the things it needs to load in HEAD at run time. The webskin cache technology is really *very* cool. But no doubt it has the odd rough edge that needs polishing. -- geoff http://www.daemon.com.au/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
