I am running 4-0-6 (1252). I am keeping up with the nightly downloads from
Jeff Coughlin's site.
I don't see how the request.inHead values currently have any hope of getting
saved with the webskin cache.
In the types.cfc getview function we have:
<cfset stCurrentView.inHead = structNew() />
<cfset stCurrentView.inHead.stCustom = structNew() />
<cfset stCurrentView.inHead.aCustomIDs = arrayNew(1) />
<cfset arrayAppend(request.aAncestorWebskins, stCurrentView) />
<!--- Include the View --->
<cfsavecontent variable="webskinHTML">
<cfinclude template="#WebskinPath#">
</cfsavecontent>
<!--- If the current view (Last Item In the array) is still OkToCache --->
<cfif
request.aAncestorWebskins[arrayLen(request.aAncestorWebskins)].okToCache>
<!--- Add the webskin to the object broker if required --->
<cfset bAdded = oObjectBroker.addWebskin(objectid=stobj.objectid,
typename=stobj.typename, template=arguments.template,
html=webskinHTML, stCurrentView=stCurrentView) />
</cfif>
I note that _farcryOnRequestEnd is not cfincluded with the webskin template
so all that logic does not run. But _farcryOnRequestEnd does not do anything
for stCurrentView anyway that I can si. And _farcryOnRequestEnd does not
even store the output from request.inhead.swfobject into inhead.stCustom or
inhead.aCustomIDs anyway.
I'm lost... Is the request.inhead functionality designed for the non-cached
webtop?
Derek
> 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.
> -----Original Message-----
> From: [email protected]
> [mailto:[EMAIL PROTECTED] On Behalf Of modius
> Sent: Thursday, August 09, 2007 9:14 PM
> To: farcry-dev
> Subject: [farcry-dev] Re: request.inhead vs objectbroker webskin cache
>
>
> 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?
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
