Are SeContainer and SeContainerInitializer safe for concurrent use by multiple threads? The string "concurren" shows up only four times in the 2.0 specification but not in this context.

I'm most interested in whether it is guaranteed that one thread may call SeContainer::initialize and another may call SeContainer::close.

I'm assuming that this is not guaranteed.

Best,

Laird