RE: xPLHal scripting matches

[Kevin Hawkins]

> -----Original Message-----
> From: Ian Lowe
> Sent: 11 September 2003 11:17
> Subject: Re: [ukha_xpl] xPLHal scripting matches
>
> > I'm not sure how difficult this would be but is a possible
solution
> to
> have
> > a flag on the filter to indicate it it is part of the first match
or
> always
> > match list. That way when a message comes in it goes down the
first
> match
> > list until it finds a match and executes that message then it
scans
> down
> > the always match list of filters executing all scripts it finds.
> >
> > S.
>
> Well...
>
> if you put it that way.. the device matched scripts (matching on the
> vendor-source-instance) lend themselves very well to match once and
> drop,
> whilst the scheme matched scripts lend themselves more to an
"trigger
> all
> that match" approach.

This Iis basically true and reflects the 'gotcha' situation I have at the
moment - however when you use wildcards in the XML file you may well be
watching for say all VD* and later have a specific VDI you want to trap so
it's going to crop up in source addresses too.

>
> I'm not sure though.. having come so far, the last thing we want to do
> is to
> delve back into "rapid development" mode.

Just a thought that reflects this rapid dev pitfall ...If you change to
execute all then every filter is later compromised by the "catchall *
* * "
filter aren't they ??

>
> A bunch of people have installed xPLHal, and I feel we should try to
> restrict the amount of changes to the main engine for a wee while..

Hmm - it's going to be an awkward issue for many people this - I feel it
needs a solution or workaround - Taking my immediate problem can you
suggest
how I would be able to code my osd.display intercept ??

K