I ran into this a short while ago with an usually BIG TAF file. The TAF contained a monstrously large survey.
When caching is turned on, the first request is slow, as Tango has to read the file and then convert the XML into an internally compiled version before execution. Once this is done, all of the next requests were lightning fast. Without caching turned on, ALL of the requests were slow with a BIG TAF. One BIG TAF or many smaller TAFs could almost be compared to religious debate. I, personally, find that a TAF should contain multiple functions and/or pages when it's for one module of the web site. Take a "feedback module", for instance. I would use one TAF for that even though there's more than one "page" or function, i.e. the form itself, the acceptance and insert/emailing of the feedback with a "Thank You" page, and an error page in case the user did not fill in the form correctly. This is a strategy that generally works best for me, but then I don't always do this. I've put a whole site in one TAF once. Another time I broke up a web site into many small TAF files. In these cases it seemed to make sense for the site and worked out well. I would guess that you too will find a strategy that works best for you and you'll modify it based on the needs of your team and of the site. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Troy Sosamon Sent: Friday, July 12, 2002 3:01 PM To: Multiple recipients of list witango-talk Subject: Witango-Talk: TAF/TML file size What are the limitations on the size of a TAF or TML file? I have never heard anyone mention any limits? What are the potential problems of large files? Troy Sosamon ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
