Talk:Privileged API
From APIDesign
(Difference between revisions)
(Comment provided by Eminnahiz - via ArticleComments extension) |
m (Reverted edits by 94.100.25.194 (Talk); changed back to last version by JaroslavTulach) |
||
| Line 19: | Line 19: | ||
--[[User:JaroslavTulach|JaroslavTulach]] 07:42, 26 May 2009 (UTC) | --[[User:JaroslavTulach|JaroslavTulach]] 07:42, 26 May 2009 (UTC) | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
Revision as of 06:53, 26 February 2011
Comments on Privileged API <comments />
Jeffrey D Smith said ...
Thanks for your comments, Jeffrey. The method names are relict of the actual Mutex class in NetBeans and they do not make much sense in separate example. Thus I've just changed the method names.
Also I've answered your question in new revision of the page.
--JaroslavTulach 07:42, 26 May 2009 (UTC)
Follow
In the readAccess(Runnable r) method, the call to lock.lock() must occur before the try block. Also, the method name "readAccess" is confusing, because it's not acquiring a read-only mutex (multi-threading), but a read-write mutex (single threading).
How do you stop unprivileged users from using the privileged constructor, thus gaining access to the privileged API?
--Jeffrey D Smith 21:48, 25 May 2009 (CEST)