On 02/05/2006, at 21:16, Kevin Dangoor wrote:
> Hi Alberto,
>
> On 5/1/06, Alberto Valverde <[EMAIL PROTECTED]> wrote:
>> My idea is that we could have a middleware.cfg file or something like
>> that which has a middleware_stack list like this:
>>
>> middleware_stack = [
>> (EvalException, ((pos_arg1, pos_arg2, ...), {kw1:X,
>> kw2:Y,..}),
>> (MyMiddleware, (.....)),
>> (etc...)
>> ]
>
> My notion in tossing evalexception in there was simply to get that
> particular functionality.
>
> Rather than creating some sort of configuration format for middleware
> like that, I'd rather go with PasteDeploy, which is the plan for
> TurboGears 1.1. I already had it running, in fact, in the firstclass
> branch. I think that application reuse is just as important as the
> ability to use middleware, andI I think we can get a working system
> with PasteDeploy in the front fairly quickly.
Great, better not reimplement any wheel then... It wouldn't be TGish :)
Haven't dig up too much in PasteDeploy and didn't know it could help
to stack middleware, going to take a look see what I find...
Alberto
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" 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
-~----------~----~----~----~------~----~------~--~---
