In my opinion, the optimal solution would enable a validation framework on top of the RPC infrastructure so that user can declare the validation/filter properties. Following an AOP approach to deal with such concerns. -- Thomas
On Jun 15, 9:32 pm, "Dean S. Jones" <[email protected]> wrote: > Such checks can be "routine" if you are using proper "server side" > validation of input. I have written several such frameworks, which > work on "generic RPC Models"... hence the validation can be routine > and generic. > > This, as I have pointed out before, is one of the dangers of using > "Domain Objects" for RPC, and trusting the client that your Domain > Objects are not ... contaminated... before you use an O/R mapper and > just persist them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
