This routine removes the args that start with an _ as it is assumed to be a "witango" control arg (_function, _start) and should not be created as a hidden field.
<@ROWS ARRAY=request$arg_names>
<@ASSIGN request$arg_name "<@COL 1>">
<@! Ignore args beginning with _ as they will be passed manually. >
<@IF "'<@LEFT @@request$arg_name 1>' != '_'">
<@! Assign the current argument values to a variable. Use TYPE=ARRAY to get all the values for multi-select lists.>
<@ASSIGN request$arg_values "<@ARG @@request$arg_name TYPE=ARRAY>">
<@! Loop through all the values for the current arg. Build a hidden form field for each. Append field HTML to existing HTML.>
<@ROWS ARRAY="request$arg_values">
<@ASSIGN request$search_vals_HTML '@@request$search_vals_HTML<input type="hidden" name="<@VAR request$arg_name>" value="<@COL 1>" /><@CRLF>'>
</@ROWS>
</@IF> <@! End ignoring args beginning with _ >
</@ROWS>
The reason for ignoring them is that they are manually added to the form action and do not need to be added as a hidden post arg.
<form method="post" action="<@APPFILE>? _function=list&_start=@@request$new_start&<@UserReferenceArgument>">
If they were not stripped out, every iteration of the next/previous functionality would add more and more of the same arg and so you would end up with multiple values for the args controlling the loop. You would also have a http header that was continually growing in size as more and more hidden post args are created. If you want to see the affect, do a global change on _function to function in a search builder. Turn debug on and look at the post args that are passed through. In this situation, after quite a few next iteration, you will see a slow down in both the web server and witango server as they have to process an every increasing number of post args in the http header.
Witango Support
On 02/06/2004, at 7:32 AM, Scott Cadillac wrote:
Hi Jamileh,
I'm not sure about the "_function" argument, but I have a vague memory of an
engineer confiding in me at a Conference once that if you include the
following argument in a TAF file request - the Server automatically goes
into Secret-double-hyper-overdrive and will run 200% faster.
http://www.mydomain.com/some.taf?_function=list&PhilIsAGod=true
Or was it "PervasiveBits=true"?
I can't remember which, except it started with a "P". If I could remember
which Conference it was (I've been to a few), than that might help me
remember.....
. . . . . . . Sorry to make you a victim of my deprived humor Jamileh :-)
No, I don't believe there is any truth to it. I think this question was
brought up in the past, but my understanding is that "_function" is simply a
training standard, so is widely adopted.
I'm just in a weird mode today, can't ya tell?
________________________________
From: Wilcox, Jamileh (HSC) [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 2:50 PM To: [EMAIL PROTECTED] Subject: Witango-Talk: Question about argument names
I seem to remember reading something on the list about it being
preferable to use the argname _function, because Witango recognizes that and
will process faster. I've tried to find the original posts but no luck.
Can anyone give me more info on this? Is it true? Are there other key argnames that I should use when possible?
Thanks much!
_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
