On 10 January 2011 04:28, BrianTheLion <[email protected]> wrote:
> Bump?
>
> On Jan 1, 9:59 am, BrianTheLion <[email protected]> wrote:
>> All,
>>
>> I mentioned some time ago that I was working on an essay about
>> functional encapsulation in pylons. As a point of reference I'm
>> interested to know how other people are dealing with the following FE
>> problem, one that I also encounter in my code:
>>
>> You're building an application that's composed of a number of distinct
>> capabilities, say a wiki, instant messaging, and shopping cart
>> functionality. You plan to wrap the whole application with a single
>> authentication mechanism. How do you do it? Which facilities in the
>> pylons suite do you use to build and test each of the capabilities
>> independently? Which do you use to integrate those independent
>> capabilities into the final application?
>>
>> I'd love to hear, especially, from folks who've been doing this for a
>> while. There's an issue of *process* that I'd like to treat as
>> thoroughly as the issue of code. What's your process?
I haven't actually done anything with pyramid yet, still working
through much the same questions you ask. This snippet:
def __call__(self, view):
return self.attr_wrapped_view(
self.predicated_view(
self.authdebug_view(
self.secured_view(
self.owrapped_view(
self.decorated_view(
self.rendered_view(
self.mapped_view(view))))))))
from this blog post:
http://plope.com/pyroptimization
has been guiding my thoughts since I read it.
Cheers,
Tony
--
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.
