Jorge Godoy wrote: > Jeff Watkins <[EMAIL PROTECTED]> writes: > >> Well, SecureResource was intended to be a mix-in class that you might add to >> an existing controller. And that existing controller might already be >> derived from a controller class. > > This is how we secure the whole class without adding decorators to everything, > right? There's an example of this in the "non-trunk" ML archives. > > On the other hand, other classes we're inheriting also have "Controller" > suffix, instead of "Resource". > > I believe consistency would be good. And we would keep with the "MVC" naming > scheme without adding a fourth term (Resource... What is a resource? When to > use one? What's its difference to a Controller/View/Model? Is a library a > resource as well? etc...).
+1 on the SecureController ... or maybe SecureMixin to emphasise it's a mix-in. Cheers, Simon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk -~----------~----~----~----~------~----~------~--~---
