On 18/9/03 5:17 pm, "J�rg Walter" <[EMAIL PROTECTED]> wrote:
> Am Thursday, 18. September 2003 16:18 schrieben Sie: >> On 18/9/03 2:42 pm, "J�rg Walter" <[EMAIL PROTECTED]> wrote: >>> Am Thursday, 18. September 2003 15:32 schrieben Sie: >>>>> For a development site, I strongly recommend AxNoCache on. >>>> >>>> Yup, that�s our setup. However we get newsfeeds etc from third parties >>>> that are included within our live site using xi:include, the feeds get >>>> up dated regularly and its these that I'm having the problems with. >>> >>> At which point are they included? In XML loaded for XSP? Or for XSLT? Or >>> something else? >> >> They are included in the parent XML / XSP page, like so; >> >> <?xml version="1.0"?> >> <?xml-stylesheet href="." type="application/x-xsp"?> >> <?xml-stylesheet href="/style/xsl/html/editorial.xsl" type="text/xsl"?> >> >> <xsp:page xmlns:xsp="http://www.apache.org/1999/XSP/Core" >> xmlns:Kentucky="http://www.kentucky.com/xsp/Kentucky/" >> language="Perl"> >> >> <channel> >> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" >> href="/content/news_feed.xml"/> >> </channel> >> </xsp:page> > > Why XSP for that? I don't see any taglib tags. You can use XInclude with plain > XML, no XSP needed. > > And in this case, XSP is the reason why caching is wrong: XSP caches the > generated perl code in memory and/or on disk. It only checks the time stamp > of the source file, not of included files -- unlike the regular AxKit cache, > which checks everything. > It is an XSP page I removed tags etc to save from posting the entire file to the groups. The tags used by the page are defined as such; <channel> <Kentucky:Login/> <Kentucky:Polls/> <Kentucky:Chart id="1" items="5" medium="1" genre="" alpha="" developer="" publisher=""/> <Kentucky:Chart id="2" items="5" medium="2" genre="" alpha="" developer="" publisher=""/> . . . So from what the sounds of what you saying if the include is used within an XSP page there is no way round the caching. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
