• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

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

ItemTemplate
Summary Exclusive access to handlers for Plugins
ReportedBy TWiki:Main.ThomasWeigert
Codebase ~twiki4
SVN Range TWiki-4.1, Sat, 23 Sep 2006, build 11571
AppliesTo Engine
Component

Priority Enhancement
CurrentState New
WaitingFor

Checkins

TargetRelease n/a
Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r3 - 2006-10-01 - PeterThoeny
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback