RE: xPLHal scripting matches

[Tony Tofts]

> - I hadn't anticipated any concurrency in the scripts (
> multiple threads ) - haven't really thought if that would be
> advantageous or complex, requiring a lock mechanism to
> guarantee the correct order of execution.

There is no order of execution, messages are processed as received.
That's the concept behind xplhal, and not something I'd want to change.

Each message received spawns a separate thread.
That thread searches for the first existing script match and executes it.
Although the loop could actually continue and look for further matches, I'm
pretty sure that once a script is launched it is independent, and therefore
the scripts would be concurrent as well as the messages.

The fact that my rather complex meteor script, which does database lookups
etc via xpl message works fine, proves the concept in my opinion

I feel trying to force a sequential processing order would put an
artificial
limitation into the system

Regards
Tony