> :> Here's a method I use: instead of writing to the database on every new
> :> page, just drop the entire form structure into every page as hidden
> :> fields.
> I thought about it, but this particular application has close to 650
> fields, and I was a little worried about carrying that many from one
> page to the next. Would have been a hell of an insert statement at
> the end of it all. Made more sense to write each page.
> JavaScript history approach, along with instructions not to use the back
> button while filling out the form, seems to d the trick for this
> particular application.
> Has anybody ever "measured" the amount of variables that could be carried
> from one page to another? Surely there's a limit somewhere before the
> server starts to bog down or cause problems.
With form fields which are actually displayed I know that you tend to run
into issues of the client browser not having enough memory to properly
display them long before the server has any problems. Particularly with
select boxes. I remember in the school management app I was working with not
too long ago they had a problem with teachers trying to enter grades on
Win98/MSIE 5 ...
The grade entry page had one row for each student, with a drop down with
numbers from 0 to 100 ( with a gap from 1-59 because it was policy to not
give grades between 0 and 59 in order to inflate gpa's ) ... which I thought
was a hideous design in the first place ...
In any event, IE started being unable to display the form page properly
after somewhere in the neighborhood of 30 students in a given class... which
came out to about 1260 individual options... I replaced the select boxes
with text fields and validated them and that solved the problem.
Getting back to your question, I would assume that the hidden form fields
still take up memory on the client machine, although I wouldn't know how
much. I suppose you could test it out by creating a cfloop that creates
hidden form fields with random values, i.e.
<cfoutput>
<cfloop index="x" from="1" to="1000">
<input type="hidden" name="#x#" value="#createuuid()#">
</cfloop></cfoutput>
put a few other visible fields in the form -- a select box, a couple text
fields and a text area, then scroll the window and see if the visible form
elements create trails that don't go away when you stop scrolling.
Isaac Dealey
Certified Advanced ColdFusion Developer
www.turnkey.to
954-776-0046
______________________________________________________________________
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
