PHP 클래스 Doctrine\Common\Cache\RiakCache

부터: 1.1
저자: Guilherme Blanco ([email protected])
상속: extends CacheProvider
파일 보기 프로젝트 열기: doctrine/cache

공개 메소드들

메소드 설명
__construct ( Riak\Bucket $bucket ) Sets the riak bucket instance to use.

보호된 메소드들

메소드 설명
doContains ( $id )
doDelete ( $id )
doFetch ( $id )
doFlush ( )
doGetStats ( )
doSave ( $id, $data, $lifeTime )
resolveConflict ( string $id, string $vClock, array $objectList ) : Riak\Object On-read conflict resolution. Applied approach here is last write wins.

비공개 메소드들

메소드 설명
isExpired ( Riak\Object $object ) : boolean Check if a given Riak Object have expired.

메소드 상세

__construct() 공개 메소드

Sets the riak bucket instance to use.
public __construct ( Riak\Bucket $bucket )
$bucket Riak\Bucket

doContains() 보호된 메소드

protected doContains ( $id )

doDelete() 보호된 메소드

protected doDelete ( $id )

doFetch() 보호된 메소드

protected doFetch ( $id )

doFlush() 보호된 메소드

protected doFlush ( )

doGetStats() 보호된 메소드

protected doGetStats ( )

doSave() 보호된 메소드

protected doSave ( $id, $data, $lifeTime )

resolveConflict() 보호된 메소드

Specific needs may override this method to apply alternate conflict resolutions. {@internal Riak does not attempt to resolve a write conflict, and store it as sibling of conflicted one. By following this approach, it is up to the next read to resolve the conflict. When this happens, your fetched object will have a list of siblings (read as a list of objects). In our specific case, we do not care about the intermediate ones since they are all the same read from storage, and we do apply a last sibling (last write) wins logic. If by any means our resolution generates another conflict, it'll up to next read to properly solve it.}
protected resolveConflict ( string $id, string $vClock, array $objectList ) : Riak\Object
$id string
$vClock string
$objectList array
리턴 Riak\Object