On Thursday 03 October 2002 10:15 am, Riley James wrote: Hmmm, you have a point there...
Maybe it is a lexical closure issue. The only sure way to find out is to review the XSP generated code (not a big hassle really if you know what to loook for). The question is what is different between the values that do get held onto and those that don't? I doubt PerForm itself generates code that treats any one type of field differently than another. My theory is that you have a closure, so the first few times you submit, things work OK because different children get each request, but as they handle it they establish whatever values are current for the form fields within the closure, which then 'stick' so that the next time you submit to the same apache child you get the same results. On thing to do in a debug environment is to run Apache in single tasking mode with no children. In that case my bet is you will see totally consistent stickiness. > This isn't cache, except PerForm's internal. Or maybe mod_perl lexical > closure issue? > > Apparently only *some* of the values are maintained by PerForm. For > example, I have a Title, Keywords, Description, and URL dialog. If I hit > "submit" on the blank returned form (after it's submitted the first time), > then my validators die saying that Keywords and Description are required. > Title and Description are then filled in. Any cache would cache all those > values. > > -- Ryan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
