Clarification on AjaxObserveField and AjaxUpdateContainer Interaction
Clarification on AjaxObserveField and AjaxUpdateContainer Interaction
- Subject: Clarification on AjaxObserveField and AjaxUpdateContainer Interaction
- From: Roger Perryman <email@hidden>
- Date: Mon, 09 May 2011 12:31:07 -0400
Hi,
I placed a WOConditional inside an update container so I could use it
as a hook to execute some code whenever the container was updated.
Specifically, I needed to update some objects after an AjaxModalDialog
was closed with the results from AjaxAutoComplete (and other inputs).
The entire page is regenerated even though only a portion of the page
is actually updated in the browser. Everything outside of the update
container appears to be discarded.
This is counter-intuitive. I was under the impression that WO
determined which container (if any) needed updating and regenerated
the content for that container only and sent that to the browser.
Because AjaxAutoComplete sends requests as you are typing, the
conditional is getting called excessively even though it was not
associated with (or inside) the update container in the parent page.
For complex pages this can be very costly.
Am I violating some sort of Ajax Commandment? What is the best way to
get around this situation? Since the popup shouldn't know anything
about the caller (except what is passed as arguments), I may use
notifications on the add button so that anyone interested can respond.
This wont solve the performance issues due to constant updates to the
page.
I am using WO 5.4. Thanks for any suggestions.
Roger
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden