hi all, I am in the process of writing an intermediate release of SEC (2.4.2) that will incorporate a few of changes - like the introduction of variables for context lifetimes in rule definitions. It seems natural to allow the use of time variables for 'event' action also - however, there is a nasty action parsing issue that doesn't make such change easy. At the moment, the 'event' action definition has the following syntax:
event [<integer>] [<event text>] If <integer> is present, event will be generated after <integer> seconds, otherwise immediately. If we now allow variables (i.e., an arbitrary string) in place of integer, an ambiguity is introduced, e.g., should the action 'event %CISCO FAULT' be interpreted as "generate the event '%CISCO FAULT' immediately", or "generate event 'FAULT' after %CISCO seconds" (where %CISCO is a user-defined variable)? In order to overcome this ambiguity, I've been thinking about adding event2 action to SEC action set that would have the following syntax: event2 <time> [<event text>] 'event2' would be identical to 'event', except <time> parameter is mandatory and may contain other symbols than numerals (0-9) only. Note that there is also another option - drop the idea of having 'event2 <variable_time> <event_text>', and use create <context> <variable_time> (event <event_text>) instead. In other words, when variable lifetimes are allowed for contexts, 'event2' can be actually expressed through 'create'. Any ideas? br, risto ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Simple-evcorr-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
