Hello, Regarding the authorization bit, as of repoze.what 1.1 (whose first alpha is going to be released by the end of this month), it's going to be possible to have that sort of pluggable authorization rules too thanks to the implementation of ACLs.
With repoze.what 1.0.X, you can only have authorization rules have to be attached to your controllers or controller actions. Cheers, - Gustavo. flzz said: > Greetings all, my company is currently in the process of migrating to > python + pylons as our development platform of choice. We currently > have a good bit of traffic to support and to help ease maintenance and > operation overheads we will be creating multiple pylons applications > to service certain aspects of our application on the whole. To the > question. Is it possible to have a single Authentication and > Authorization model (repoze.who repoze.what) that is shared among > multiple pylons applications? We currently utilize the debian > packaging system (Ubuntu) to handle software deployment, so the > approach I can see us taking is to abstract out the A&A portion of the > system into its own package (deb/egg). Then from that point we will > create our own pylons template that includes the use of this system. > Am I off base with this approach at all? it seems uniformity of WSGI > and the modular nature of pylons should make this doable. > > Thanks! -- Gustavo Narea <xri://=Gustavo>. | Tech blog: =Gustavo/(+blog)/tech ~ About me: =Gustavo/about | -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
