[Catalyst-dev] Plugin or controller?

[Matthias Dietrich]

Hi,

> So, first, there is no such thing as  
> Catalyst::Plugin::Authorization.  When you first mentioned it I  
> assumed you simply meant Authorization::ACL or  
> Authorization::Roles.  The latter should not be a plugin in my  
> opinion, but a model.

sorry, I meant Plugin::Authentication - sorry for that!  But as I  
understand it, not every plugin module on CPAN should be a plugin?   
But when this is based on opinions, who decides which is a plugin and  
which not?

> If you are trying to access an application wide object, it's a  
> model.  As such, I again restate that  
> Catalyst::Controller::RateLimit should simply be either a  
> Catalyst::Model::Adaptor or a customized Model.  It shouldn't be a  
> controller or a model, since it does have a benefit of being  
> application wide.

I guess you meant "It shouldn't be a controller or a plugin", right?

Don't get me wrong, I don't want to create this as a plugin under all  
circumstances.  I just want to figure out when a module is a plugin,  
when a model and when a controller.  But I'm getting closer to the  
truth ;).

matt

-- 
rainboxx Matthias Dietrich
Freier Software Engineer

rainboxx                  |  Tel.: +49 (0) 151 / 50 60 78 64
Tölzer Str. 19            |  Mail: matt at rainboxx.de
70372 Stuttgart           |  WWW : http://www.rainboxx.de

XING: https://www.xing.com/profile/Matthias_Dietrich18
GULP: http://www.gulp.de/profil/rainboxx.html



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: Signierter Teil der Nachricht
Url : http://lists.scsys.co.uk/pipermail/catalyst-dev/attachments/20090601/e060a5c1/PGP.pgp