How to handle actionlib conflicts
Is there any pre-existing strategy for preventing conflicting actionlib actions from running at the same time?
Say I write two action servers to 1) wander around aimlessly, and 2) goto a specific location. Is it up to me to write code to ensure they don't run at the same time, or is there an existing mechanism to help prevent this?
Ideally, I'd like to design actions the way a database regulates transactional access to tables. Each action should publish a list of resources that it "locks", and while it's running, no other action that requires those same resources should be able to run.