org.logicalcobwebs.concurrent
类 WriterPreferenceReadWriteLock.WriterLock

java.lang.Object
  继承者 org.logicalcobwebs.concurrent.WriterPreferenceReadWriteLock.Signaller
      继承者 org.logicalcobwebs.concurrent.WriterPreferenceReadWriteLock.WriterLock
所有已实现的接口:
Sync
包容类:
WriterPreferenceReadWriteLock

protected class WriterPreferenceReadWriteLock.WriterLock
extends WriterPreferenceReadWriteLock.Signaller
implements Sync


字段摘要
 
从接口 org.logicalcobwebs.concurrent.Sync 继承的字段
ONE_CENTURY, ONE_DAY, ONE_HOUR, ONE_MINUTE, ONE_SECOND, ONE_WEEK, ONE_YEAR
 
构造方法摘要
protected WriterPreferenceReadWriteLock.WriterLock()
           
 
方法摘要
 void acquire()
          Wait (possibly forever) until successful passage.
 boolean attempt(long msecs)
          Wait at most msecs to pass; report whether passed.
 void release()
          Potentially enable others to pass.
 
从类 java.lang.Object 继承的方法
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

构造方法详细信息

WriterPreferenceReadWriteLock.WriterLock

protected WriterPreferenceReadWriteLock.WriterLock()
方法详细信息

acquire

public void acquire()
             throws InterruptedException
从接口 Sync 复制的描述
Wait (possibly forever) until successful passage. Fail only upon interuption. Interruptions always result in `clean' failures. On failure, you can be sure that it has not been acquired, and that no corresponding release should be performed. Conversely, a normal return guarantees that the acquire was successful.

指定者:
接口 Sync 中的 acquire
抛出:
InterruptedException

release

public void release()
从接口 Sync 复制的描述
Potentially enable others to pass.

Because release does not raise exceptions, it can be used in `finally' clauses without requiring extra embedded try/catch blocks. But keep in mind that as with any java method, implementations may still throw unchecked exceptions such as Error or NullPointerException when faced with uncontinuable errors. However, these should normally only be caught by higher-level error handlers.

指定者:
接口 Sync 中的 release

attempt

public boolean attempt(long msecs)
                throws InterruptedException
从接口 Sync 复制的描述
Wait at most msecs to pass; report whether passed.

The method has best-effort semantics: The msecs bound cannot be guaranteed to be a precise upper bound on wait time in Java. Implementations generally can only attempt to return as soon as possible after the specified bound. Also, timers in Java do not stop during garbage collection, so timeouts can occur just because a GC intervened. So, msecs arguments should be used in a coarse-grained manner. Further, implementations cannot always guarantee that this method will return at all without blocking indefinitely when used in unintended ways. For example, deadlocks may be encountered when called in an unintended context.

指定者:
接口 Sync 中的 attempt
参数:
msecs - the number of milleseconds to wait. An argument less than or equal to zero means not to wait at all. However, this may still require access to a synchronization lock, which can impose unbounded delay if there is a lot of contention among threads.
返回:
true if acquired
抛出:
InterruptedException


Copyright © 2014. All rights reserved.