On 2014-08-18, sebb wrote:

> I suspect just using a volatile enum would be sufficient as enums are
> thread-safe so it is just necessary to ensure safe publication.

I went with the volatile route since the code never used compareAndSet
or one of its friends anyway.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to