Re: xPLHal scripting matches

[steve.cooper@xxxx]

OK this time in English, busy day sorry guys:

Just to add my thoughts on this issue. I think the first match approach
makes more sense. If you want to match something specifically you can, if
there is no match it can then be picked up by a catch all routine. If you
go with an all matching filters appraoch you lose the ability to have a
catch all routine because the routine will not know if anything else has
acted on the message. I can see how Kevin's issue however.

I'm not sure how difficult this would be but a possible solution might be
to have a flag on each filter to indicate whether it is part of a 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.



___________________________________________________________________________
The information contained in this message is confidential and may be
legally privileged. If you are not the intended recipient, please do not
read, copy or otherwise use it and do not disclose it to anyone else.
Please notify the sender of the delivery error and then delete the
message from your system.
Any views or opinions expressed in this email are those of the author only.
Communications will be monitored regularly to improve our service and for
security and regulatory purposes.
Thank you for your assistance.
___________________________________________________________________________