Re: Override events

[Scott Gray]

Another approach could be to add a disable attribute to the event element, that way you could just disable an event by redefining it with disabled="true" and then you could either define a new event or not depending on what you were trying to achieve, WDYT?

Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 1/04/2009, at 10:52 PM, Bilgin Ibryam wrote:

On Apr 1, 2009, at 12:24 PM, David E Jones wrote:

On Apr 1, 2009, at 3:13 AM, Bilgin Ibryam wrote:

On Mar 17, 2009, at 10:55 PM, David E Jones wrote:

A name or some sort of an identifier on each might be a good way to go...

-David

David, thanks for the advice.

Do you mean a new optional "name" attribute on event element, so that events with the same name (inside firstvisin, preprocessor... ) will be overridden ?

Yes, that is what I meant.

OK, then I will add an optional name attribute. Optional because this attribute will not be used in request events.

Bilgin

Or you mean a new "name" attribute on firstvisin/preprocessor/ postprocessor.... elements so we will be able to replace all the events inside these elements at once?

-David

This would be more or less the same as just overriding the entire block all the time, ie probably not as useful.

smime.p7s
Description: S/MIME cryptographic signature