I had some thoughts on Dan's most recent post: http://www.model-glue.com/blog/index.cfm/2009/11/24/MG-32-Feature-Sneak-Peak--Input-Sanitization
Overall seems like a fine featue. I'd recommend the MG team defines a security/sanitization interface, create a service then that uses portcullis to do the data sanitization and implements the interface. That way someone else could swap that out for something else. Other than that, looks like a fine idea. Maybe the option to disable it might be nice as well... Doug Hughes, President Alagad Inc. [email protected] 888 Alagad4 (x300) Direct: 651 Alagad4 (651-252-4234) Fax: 888-248-7836 -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" 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/model-glue?hl=en
