Yes, it makes sense. This way I can have several result objects, for different validations (different objects), in the same view.
Ronan Baz escreveu: > I think Brian's result object is a generic one that can be re-used > with any change operation. Something along the lines of: > > * Status (i.e. Success/Fail) > * StatusCode (i.e. User.Validation.Error) > * Message (i.e. There were some validation errors in the user object) > * Payload (i.e. contains a structure of validation errors, or a > proper business object - depending on the whether the operation > was success or fail) > > The view would check the status of the result object to see how to > handle the payload. > > Correct me if I am wrong Brian... > > Baz > > > On Wed, Jul 16, 2008 at 1:09 PM, Ronan Lucio <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > Brian, > > Brian Kotek escreveu: > > No Result is only returned during change operations, i.e. saving a > > User. For list operations I just return the query, because there can > > be no validation failures for simply *getting* something. Hopefully > > that makes sense. > > Yeap. That's clear. > > Thank you once again, > Ronan > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
