But I still think people will have serious problems with this. If it's the script-writer that is locking the resources, the script-runner doesn't know which of the scripts will win out. The script-runner needs to have intimate knowledge of the scripts.

Most script-runners will probably just halt the port buydown while they do their citkill. They don't want the port buydown obtaining use of the network and interfering with the citkill.

I too am eagerly awaiting testing out this whole event driven stuff. I too agree with Astrochimp on many of these issues. But i'll wait and see how it actually performs and works.

It's only necessary to do so when sending a burst. When responding to a single event, locking and unlocking are automatic.