[Catalyst] Authentication gotchas

[John Wang]

Is inheriting all the plugins the way to go? It seems like there are
situations where an app will use a lot of plugins and it might be difficult
for the various plugin writers to ensure there are no namespace collisions
with every other plugin out there.

I like the general situation where each plugin is granted a single $c level
accessor, e.g. C::P::Prototype where everything is accessed through that
accessor, like $c->prototype->method. This is easy to do when there is a
C::Plugin wrapper, however it would be nice if that was the default behavior
when a wrapper isn't used. A benefit of this is when an app would like to
change the plugin accessor name, you just need to change it in a single
location and everything will still work.

--
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rawmode.org/pipermail/catalyst/attachments/20051217/494ae769/attachment.htm