My applications use @include in every hit to the server and I've never
had a problem like the one you describe.....
/John
Roland Dumas wrote:
On 10/15/04 8:54 AM, "John McGowan" <[EMAIL PROTECTED]> wrote:
Hold on... Why wouldn't you be caching application files or include
files? I've never heard of anybody not doing that in a production
environment.
I'm on 5.0, but I ran into a strange behavior when caching tafs:
IF one uses ANY includes, perhaps just one in the request cycle, each time
the cached taf is called, it increments the # of includes uses until it
reaches the maximum and errors out.
That's ANY includes in ANY tafs in ANY domain and witango will throw errors
in all domains for tafs using includes.
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
