Even tho this is an old thread, i wanted to dive in. Great discussion around AJAX & "traditional" html forms processing.
We are currently seeing a huge disadvantage of AJAX--at least the way this particular app is written. We have huge pipes, so returning to the server is not an issue. Nevertheless, AJAX was chosen apparently for its "cool" factor & the intial update form takes 40 seconds to load because it's a multi-page form with a lot of fields. All the data for those fields must be held in memory & parsed by the workstations--some of which are old. Obviously it could still be written to update the db each time a page is submitted or changed, but then it's not as AJAX & it's not as cool. So sometimes it depends on the nature of the application. I have built a change log successfully by querying the "before" tables at the start of the action page, using a loop thru the form fields to compare the db values to the form values. If different, I write the pertinent record to a log table. The user comes from login info stored as client or session var. There's very little script involved--only a few lines. The list of form fields and the list of table fields are both variables. CF compares values in fields very fast. If the field names don't match, a view with aliases fixes that pretty easily. The whole thing could be a custom tag or expression. I really appreciated reading a whole thread with no personal attacks. Sometimes I think we are on too much caffeine and operate in the "fight or flight" mode. Anyone disagrees with us & we bare our fangs. Ted ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Macromedia ColdFusion MX7 Upgrade to MX7 & experience time-saving features, more productivity. http://www.adobe.com/products/coldfusion?sdid=RVJW Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:283932 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
