Hi All,
Anyone know the performance implications of using databinding to
update a model vs an 'updateModel()' type call?
I can use basic databinding to bind a form to the model
(source="{foo.customer_name}") and databinding calls to bind
foo.customer_name back to the form control (so your model is updated
everytime a form field is updated). This has the advantage that your
model is always up to date with respect to the form - no extra
processing required.
I could also just use the basic databinding to bind the form controls
to the model, and an UpdateModel(m:Model) call to grab the contents of
all the fields and shove them back into the model. This requires an
extra function call to 'sync' the model with the form, but skips all
the event handling (for instance, if you update the 'customer_name'
control 3 times, you only update the model once at the end)
Anyone know how much of a load data binding/event processing puts on
the system with a moderately complicated app? I'm figuring 10-20
tables of 20-40 fields each. This is for a data entry app, so users
will be in all parts of the app all day long. Should I be looking at
un-binding models when they are not used/active (ie, if you switch
from clients to vendors, should I unbind the fields on the 'clients'
model ?)
steve
