On 11/19/01 5:55 PM, "Jon Stevens" <[EMAIL PROTECTED]> wrote:
> on 11/19/01 2:39 PM, "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote: > >> To the best of my recollection, what happens is that that as you chain, the >> EC gets 'pulled' forward when the chain happens, so if you have a context >> with an EC that gets wrapped a few times, that EC will be available *unless* >> someone attaches their own EC somewhere during the wrap sequence. > > Ok, that *sounds like what I need*. Essentially, Turbine has a global > context which contains all the other scoped contexts (which are created by > the Pull Service). I want to attach the EC's to the global context so that I > don't have to worry about also attaching them to the scoped contexts. > > I understand that you implemented it this way for max configuration ability > (as well as befor the VelocityEngine was created), but it would have been > better to simply be able to bind the EC to the VE and let Velocity worry > about which contexts it goes to. You can't do that with mutiple threads. You may want to do different things for each request... > > BTW, the reason why I'm *finally* getting around to playing with EC's is > that I have wanted to create an EC that auto filters for cross site > scripting when a $var is rendered. :-) Transparent CSS resolution in the > templates. Coooool... > >> There is no EC chaining (although there was in the first rendition and there >> could be again...) > > I don't think I need that quite yet... No - it's problematic anyway :) -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting "Whoever would overthrow the liberty of a nation must begin by subduing the freeness of speech." - Benjamin Franklin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
