Comments on: Slides, links and source from the Ajax Monorail talk http://gojko.net/2008/06/13/slides-links-and-source-from-the-ajax-monorail-talk/ Building software that matters Thu, 02 Feb 2012 07:12:46 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: gojko http://gojko.net/2008/06/13/slides-links-and-source-from-the-ajax-monorail-talk/comment-page-1/#comment-31633 gojko Sun, 03 Aug 2008 15:07:58 +0000 http://gojko.net/?p=138#comment-31633 Hi Rodney, you can see the video also here: http://video.google.com/videoplay?docid=-383418991140556188 Hi Rodney,

you can see the video also here: http://video.google.com/videoplay?docid=-383418991140556188

]]> By: Rodney http://gojko.net/2008/06/13/slides-links-and-source-from-the-ajax-monorail-talk/comment-page-1/#comment-31632 Rodney Sun, 03 Aug 2008 14:38:10 +0000 http://gojko.net/?p=138#comment-31632 I enjoyed the slides. Can you tell me where the video is as the one at http://skillsmatter.com/podcast/open-source-dot-net/developing-ajax-web-applications-with-castle-monorail never plays? Thanks. I enjoyed the slides. Can you tell me where the video is as the one at http://skillsmatter.com/podcast/open-source-dot-net/developing-ajax-web-applications-with-castle-monorail never plays?

Thanks.

]]> By: gojko http://gojko.net/2008/06/13/slides-links-and-source-from-the-ajax-monorail-talk/comment-page-1/#comment-28658 gojko Tue, 17 Jun 2008 07:07:50 +0000 http://gojko.net/?p=138#comment-28658 Hi Danyal, I'm not sure that I understand what you are getting at. Format validation is fairly cheap, so there is little harm in validating the whole object every time (and that will also make sure that any inter-field dependencies are validated as well). Having said that, if you use castle component validations, and you know which field you want to validate, then you can get the validation attribute on that actual property and execute the validation yourself. See the source code for <a target="_blank" href="http://svn.castleproject.org:8080/svn/castle/trunk/Components/Validator/Castle.Components.Validator/ValidatorRunner.cs" rel="nofollow">ValidationRunner.cs</a> — that should help you with validating individual properties. Hi Danyal,

I’m not sure that I understand what you are getting at. Format validation is fairly cheap, so there is little harm in validating the whole object every time (and that will also make sure that any inter-field dependencies are validated as well). Having said that, if you use castle component validations, and you know which field you want to validate, then you can get the validation attribute on that actual property and execute the validation yourself.

See the source code for ValidationRunner.cs — that should help you with validating individual properties.

]]> By: Danyal http://gojko.net/2008/06/13/slides-links-and-source-from-the-ajax-monorail-talk/comment-page-1/#comment-28591 Danyal Sat, 14 Jun 2008 20:07:42 +0000 http://gojko.net/?p=138#comment-28591 Hi Gojko Thanks for the talk - I found it really useful. Maybe you remember me as somebody who asked a question about validation when developing Ajax applications. I wasn't actually asking about client-side validation. For me, client-side validation is just a bit of sugar. The server-side is more important. What I am concerned about is how to keep the validation models DRY on the server side while developing applications in MonoRail that involve both normal form submissions (for example, to submit a form to create a new expense) and AJAX form submissions (for example, to edit the date of that expense, later). If databinding is used with each, you need two separate transport models for these two submissions, because you don't want the validators of the whole form to be executed when you are just editing one field. So there is some repetition and the validation is no longer DRY. And every new AJAX action needs another transport model decorated with validation attributes. I think RoR tries to solve this by specifying which controllers/actions a validator runs on, so you can reuse the original transport model but 'turn off' validators as necessary. Do you know if MonoRail tries to solve it? It's not a terrible thing if it can't be solved - it just means I'll have to use my copy and paste magic a bit more. Anyway thanks again and I hope to see you at another talk! Thanks Danyal Hi Gojko

Thanks for the talk – I found it really useful.

Maybe you remember me as somebody who asked a question about validation when developing Ajax applications. I wasn’t actually asking about client-side validation. For me, client-side validation is just a bit of sugar. The server-side is more important. What I am concerned about is how to keep the validation models DRY on the server side while developing applications in MonoRail that involve both normal form submissions (for example, to submit a form to create a new expense) and AJAX form submissions (for example, to edit the date of that expense, later). If databinding is used with each, you need two separate transport models for these two submissions, because you don’t want the validators of the whole form to be executed when you are just editing one field. So there is some repetition and the validation is no longer DRY. And every new AJAX action needs another transport model decorated with validation attributes.

I think RoR tries to solve this by specifying which controllers/actions a validator runs on, so you can reuse the original transport model but ‘turn off’ validators as necessary. Do you know if MonoRail tries to solve it?

It’s not a terrible thing if it can’t be solved – it just means I’ll have to use my copy and paste magic a bit more.

Anyway thanks again and I hope to see you at another talk!

Thanks
Danyal

]]>