Hi Felix,
I have just started to see this problem as well. A request for
fallback://xslt/page2xhtml.xsl seems to get cached, and is used by other
publications. Odd that I haven't seen it till now. Have you found a
solution?
Thanks,
--Doug
Felix Röthenbacher wrote:
Hi
I wonder how the fallback: protocol behaves when it comes
to caching? If several publications are in use at the same
time and resources are accessed with the fallback: protocol,
it seems that a cached resource is used instead of the resource
which applies to the current publication. Has anyone else
seen this behaviour?
Thanks for sharing your thoughts,
- Felix
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
