A Store object can be used to store session specific data. You should see it as a convenience abstraction of a Map. In Tabris some context objects exist like in {@link Swipe} or {@link Page}. These context object are using such a store to enable a loose communication between the components.
@since 0.11This class is conditionally thread-safe; {@link #wrapWith(Key)} and{@link #noWrap()} should not be called concurrently to avoidnon-deterministic {@link #save(Key)} and {@link #load()} behavior. @author darylseah@gmail.com (Daryl Seah)
Object[][] states = new Object[][]{ new Object[]{"AL", "Alabama"}, new Object[]{"AK", "Alaska"}, new Object[]{"AZ", "Arizona"}, new Object[]{"AR", "Arkansas"}, new Object[]{"CA", "California"}}; Reader reader = new ArrayReader(new RecordDef( new FieldDef[]{ new StringFieldDef("abbr"), new StringFieldDef("state") })); Store store = new Store(proxy, reader);
@see com.gwtext.client.data.XmlReader
@see com.gwtext.client.data.JsonReader
@see com.gwtext.client.data.HttpProxy
@see com.gwtext.client.data.MemoryProxy
Store
generates GraphOverTimes
by keeping track of assertions and revocations of graphs from different sources.
@author reto
There's no reason to consider append-logging at this level; all logging and locking is handled at the HRegion level. Store just provides services to manage sets of StoreFiles. One of the most important of those services is compaction services where files are aggregated once they pass a configurable threshold.
The only thing having to do with logs that Store needs to deal with is the reconstructionLog. This is a segment of an HRegion's log that might NOT be present upon startup. If the param is NULL, there's nothing to do. If the param is non-NULL, we need to process the log to reconstruct a TreeMap that might not have been written to disk before the process died.
It's assumed that after this constructor returns, the reconstructionLog file will be deleted (by whoever has instantiated the Store).
Locking and transactions are handled at a higher level. This API should not be called directly but by an HRegion manager.
use the different query methods (getXXX) to query the metadata
the query methods are string based, and does not cause the class loader to define the types
use {@link org.reflections.Reflections#getStore()} to access this store
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|