CC raised an interesting question: could there be race conditions between plugins?

As you know, all plugins sitting like runners behind the starting block waiting to jump to action when the handler is invoked. I can easily imagine scenarios where these plugins conflict. Most of the time we can sort this out by first looking through the text to see whether there is any applicable tags, but there could be cleanup actions that a plugin needs to do in the after... handlers for example, which cannot rely on tags any longer.

Should there be a way for a plugin to register an exclusive access to a handler, meaning that the other plugins won't get to run on that handler?

-- TW

Good point. Please bring enhancement requests forward in the Codev web. Create a bug item once there is an agreement on the spec.

-- PTh

This is a solution looking for a problem. If it's needed, we'll fix it.

-- CrawfordCurrie - 08 Mar 2009