> That said, there is something new to watch out for. This is not a > well-known bit of Witango, but it was found that self-calling @include > statements were problematic (especially the infinite ones), so there is > now a limitation on how many includes (nested or not) a single action > will execute. I believe it is 20.
Robert is correct. There is a limit of 20 @include tags per action. If you need more than 20 @include tags split them across multiple actions. There is no limit on the number of includes in a TAF or TCF, just per action. Witango Support On 18/11/03 11:09 AM, "Robert Shubert" <[EMAIL PROTECTED]> wrote: > Jim, > > Includes require a fetch and parse, if the include is not already in > memory or if include caching is off. This fetch could be expensive. Even > if it is memory resident, some overhead always exists. > > This isn't to say that the fetch outweighs portability benefits. The > trade-off usually works in the developers favor. > > I would recommend only loading global variables if needed (in an @IF > action/statement) and some developers like to load global variables from > a database. > > That said, there is something new to watch out for. This is not a > well-known bit of Witango, but it was found that self-calling @include > statements were problematic (especially the infinite ones), so there is > now a limitation on how many includes (nested or not) a single action > will execute. I believe it is 20. > > Robert > > > > -----Original Message----- > From: Jim Kass [mailto:[EMAIL PROTECTED] > Sent: Monday, November 17, 2003 6:31 PM > To: [EMAIL PROTECTED] Com > Subject: Witango-Talk: Performance Question... > > Hey guys, > > For those of you who have some idea of tango internals... I'm wondering > is > there any performance hit to using lots of "includes" that are common to > all > files, rather than having each file have common actions. > > In other words, if I setup 20 files with: > > <@INCLUDE FILE="header.inc"> > at the very top of the file > > AND header.inc has... > > <@INCLUDE FILE="globals.inc"> > and then some html/js code that is common to all tafs... > > AND globals.inc has (amongst other things)... > <@ASSIGN local$myGlobal "this is a global var to all tafs"> > <@ASSIGN ... > > <@ASSIGN ... > > <@ASSIGN ... > > <@ASSIGN ... > > > > Is that ANY WORSE than me putting everything that is in those same set > of > includes into one long Results action at the head of each taf. In > otherwords what I want to do is setup the equivalent of "require" or > "use" > (for those who are familar with Perl) that can help make my tafs more > portable and more manageable. > > TIA > > > Jim Kass > Web Developer > > -- > Forestweb: The Source for Industry Intelligence > Best Content -- Most Relevant -- Best Delivery > http://www.forestweb.com > (310) 553 - 0008 > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
