Roland, There is an include (@INCLUDE) call limit of 20 PER ACTION in Witango Server 5.0. This is regardless of whether they are cached or not.
This limit was introduced as there were a high proportion of server lockups linked to looping include files especially when used with branches between taf files, tcfs that call their own methods or when variables were used for the file name. On windows especially a looping include could (and did quite often) crash the OS. > If I have 2 includes, but they are in a loop that runs 20-100 times, > does that put me over a max? (each loop creates an email) Yes. 2 x 100 = 200 calls to @INCLUDE This limit has been pushed out to 75 PER ACTION in 5.5 which we believe will work with the majority of solutions and is a balance between protecting the resources and performance of the server (and OS) as well as being flexible to the programmer. Phil On 20/09/2004, at 12:58 PM, Roland Dumas wrote: > If I have 2 includes, but they are in a loop that runs 20-100 times, > does that put me over a max? (each loop creates an email) > > If I have a cached taf that calls an include, does each time that taf > is run > add toward my max # of includes? > > This is all very confusing. I'd thought the rule was the # of include > depth > (includes including other includes, etc.) ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
