Angela Lin wrote: > I agree with this proposal. > > For most of the classlib, the classlib-threading contract should be > straightforward. > > There are a couple grey areas that concern me: > - j.u.concurrent > - j.l.management (ThreadMXBean etc.) > j.u.concurrent seems to need some special VM support, and ThreadMXBean > seems to need to know way too much about the VM threading model to be > satisfied by a simple contract. > > I think someone else had suggested that parts of lang-management might > be considered kernel classes. Any thoughts?
Agreed, I expect that we will define a set of o.a.h kernel classes that provide the lang-mgmt natives. Same for some of the lock queries via j.u.concurrent as you mention in the other (e-mail) thread. Tim
