Why should I not? What's wrong about it? If I build a plugin I decide what is available to my application. And using requestAction() is perfectly acceptable and under some circumstances even recommended.
So where's the sin? -MI --------------------------------------------------------------------------- Remember, smart coders answer ten questions for every question they ask. So be smart, be cool, and share your knowledge. BAKE ON! blog: http://www.MarianoIglesias.com.ar -----Mensaje original----- De: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] En nombre de AD7six Enviado el: Jueves, 10 de Mayo de 2007 07:24 a.m. Para: Cake PHP Asunto: Plugin Controller name uniqueness. was: phpGACL installation > If in my application I have a UsersController, and need to do a > requestAction() to a plugin's UsersController, then hell breaks loose. Why would you want to do that? Because something is a technical possibility, I don't feel that should be the basis for giving Plugin controllers 'unique' names. having inbuilt namespaces for plugins would completely avoid the issue though (which of course would involve cake expecting plugin controllers to be named differently). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
