[Vm-dev] Where to get Monitor implementation based on primitives?

Ben Coman btc at openinworld.com
Wed Jan 20 14:37:07 UTC 2016


On Tue, Jan 19, 2016 at 12:06 AM, KenD <Ken.Dickey at whidbey.com> wrote:
>
> On Mon, 18 Jan 2016 11:22:15 +0100
> Denis Kudriashov <dionisiydk at gmail.com> wrote:
>
>> To choose better class name we should take into account how we will use it.
>> Could you suggest names for #acquire and #release in context of your class
>> name?
>> ("locker acquire" is not good)
>>
>> If people think that simple Lock is good for this purpose we can use it.
>
>
> Perhaps better to think of an "access permission" than a "lock"
>
> uniqueAccess acquire

Maybe.  Except when I think of uniqueXXX  what comes to mind is the
Singleton pattern.

>
> accessPermission acquire

I think this is a stretch, and invokes thoughts of security and file access.

cheers -ben


More information about the Vm-dev mailing list