[Solar-talk] Method-Based Actions

[Rob Allen]

Travis Swicegood wrote:

> 
> The larger, and just as important issue here (imo) is having the ability 
> to easily limit which methods are executable by the 
> dispatcher/front-controller when passing an action in.

Fair enough :)  appending Action is the solution then!

> 
> As for the naming, I've seen both done and both are legible.  Ideally, 
> you won't have any methods on a controller other than the actions 
> anyhow, so the documentation argument becomes moot.  Given that there's 
> reasons for both, why not handle the method mapping in an object that 
> can be replaced. 

Configuration for configuration's sake IMO. At the end of the day it 
really doesn't matter as long as whenever you pick up a Solar app, it's 
the same convention every time...

Regards,

Rob...