# Implementing ASP.NET MVC

**URL:** <https://www.ruby-forum.com/t/implementing-asp-net-mvc/160471>\
**Category:** IronRuby\
**Created:** [February 16, 2009, 7:37pm UTC](https://www.ruby-forum.com/t/implementing-asp-net-mvc/160471 "2009-02-16T19:37:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![barby](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/c57346/32.png) [@barby](https://www.ruby-forum.com/u/barby)\
**Post date:** [February 16, 2009, 7:37pm UTC](https://www.ruby-forum.com/t/implementing-asp-net-mvc/160471/1 "2009-02-16T19:37:01Z")

</div>

Hi,

I’m currently implementing ActionFilters and ActionResults in ironruby  
mvc.  
I do have some questions about that…  
Why so many filters? Is there an example somewhere so I can see their  
intended use?

At the moment I’m doing it this way:

class HomeController \< Controller  
before\_filter :some\_name do |ar|  
# do some really cool shizzit here  
end

before\_filter :some\_action

after\_filter  
around\_filter  
result\_filter  
exception\_filter  
authorize\_filter

# or

filter :some\_name, :when =\> :after do |res|; end;  
filter :action\_name, :when =\> :authorize

end

Then there are also selectors… they seem to do the same thing as  
filters  
but I might be mistaking. Can I just lump those together and just call  
it a  
different kind of filter?

What would be the best strategy because the amount of filters is a  
little  
bit over doing it IMHO ?

Cheers  
Ivan