On Sat, Oct 11, 2008 at 10:57 AM, Vinay email@example.com
thank you both for your replies!
So if we consider an invoicing application itself, what you say is
that i need to observe the fields rate, quantity, tax, etc (say)
independently, and then send in the whole form when even one field is
changed? If we take an invoice example, there are going to be fields
like invoice number, recipient, created on etc which are hardly
necessary for this calculation right?
A general rule of thumb of mine is: Consider as a first choice the
approach that is both easy and trivially robust.
In this case, submitting the form is just a matter of setting :submit
=> ‘invoice-form’ in the observers.
One could select the strictly needed fields and avoid sending the
invoice number, customer ID, etc. to save a few bytes. But that
introduces more complexity and a coupling point between the form and
So the question I ask myself is: is there some measure that justifies
that? Is the application having issues with the load or something due
to that? The answer so far is no, so I just :submit the form.