Maybe an option could be added to all view engines to change this behavior and make them more strict, taking only properties from PropertyBag. By default this option would be unset to keep backwards compatibility.
On Mar 31, 5:11 pm, Ken Egozi <[email protected]> wrote: > I personally regret that I put that on AspView when I started it. > my opinion is that View's properties should be explicitly set by the > controller, and that the view should be as http ignorant as possible. > > On Tue, Mar 31, 2009 at 10:46 PM, Mauricio Scheffer < > > [email protected]> wrote: > > > This is by design. See for example: > > >http://fisheye2.atlassian.com/browse/castleproject/trunk/MonoRail/Cas... > > >http://fisheye2.atlassian.com/browse/castleproject/trunk/MonoRail/Cas... > > > I find this quite handy... and PropertyBag always takes precedence. > > > On Mar 31, 2:05 pm, Mike Nichols <[email protected]> wrote: > > > Is it appropriate to consume the params passed in either a route > > > params or query string directly on a view without assignment into the > > > property bag by the controller? > > > I know Brail lets me do this and it is handy, but is that by design or > > > just something that happens? > > -- > Ken > Egozi.http://www.kenegozi.com/bloghttp://www.delver.comhttp://www.musicglue.comhttp://www.castleproject.orghttp://www.gotfriends.co.il --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" 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/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
