-
algoD.interpreter.parts.Storage.STORAGE
@author dusakus
-
ch.sahits.game.openpatrician.model.building.impl.Storage
-
com.extentech.formats.LEO.Storage
Defines a 'file' in the LEO filesystem. contains pointers to Block storages as well as the storage type etc. Header (128 bytes): Directory Entry Name (64 bytes): This field MUST contain a Unicode string for the storage or stream name encoded in UTF-16. The name MUST be terminated with a UTF-16 terminating null character. Thus storage and stream names are limited to 32 UTF-16 code points, including the terminating null character. When locating an object in the compound file except for the root storage, the directory entry name is compared using a special case-insensitive upper-case mapping, described in Red-Black Tree. The following characters are illegal and MUST NOT be part of the name: '/', '\', ':', '!'. Directory Entry Name Length (2 bytes): This field MUST match the length of the Directory Entry Name Unicode string in bytes. The length MUST be a multiple of 2, and include the terminating null character in the count. This length MUST NOT exceed 64, the maximum size of the Directory Entry Name field. Object Type (1 byte): This field MUST be 0x00, 0x01, 0x02, or 0x05, depending on the actual type of object. All other values are not valid. 0= Unknown or unallocated 1= Storage Object 2- Stream Object 5= Root Storage Object Color Flag (1 byte): This field MUST be 0x00 (red) or 0x01 (black). All other values are not valid. Left Sibling ID (4 bytes): This field contains the Stream ID of the left sibling. If there is no left sibling, the field MUST be set to NOSTREAM (0xFFFFFFFF). Right Sibling ID (4 bytes): This field contains the Stream ID of the right sibling. If there is no right sibling, the field MUST be set to NOSTREAM (0xFFFFFFFF). Child ID (4 bytes): This field contains the Stream ID of a child object. If there is no child object, then the field MUST be set to NOSTREAM (0xFFFFFFFF). CLSID (16 bytes): This field contains an object classGUID, if this entry is a storage or root storage. If there is no object class GUID set on this object, then the field MUST be set to all zeroes. In a stream object, this field MUST be set to all zeroes. If not NULL, the object class GUID can be used as a parameter to launch applications. State Bits (4 bytes): This field contains the user-defined flags if this entry is a storage object or root storage object. If there are no state bits set on the object, then this field MUST be set to all zeroes. Creation Time (8 bytes): This field contains the creation time for a storage object. The Windows FILETIME structure is used to represent this field in UTC. If there is no creation time set on the object, this field MUST be all zeroes. For a root storage object, this field MUST be all zeroes, and the creation time is retrieved or set on the compound file itself. Modified Time (8 bytes): This field contains the modification time for a storage object. The Windows FILETIME structure is used to represent this field in UTC. If there is no modified time set on the object, this field MUST be all zeroes. For a root storage object, this field MUST be all zeroes, and the modified time is retrieved or set on the compound file itself. Starting Sector Location (4 bytes): This field contains the first sector location if this is a stream object. For a root storage object, this field MUST contain the first sector of the mini st ream, if the mini stream exists. Stream Size (8 bytes): This 64-bit integer field contains the size of the user-defined data, if this is a stream object. For a root storage object, this field contains the size of the mini stream. ?? offset type value const? function 00: stream $pps_rawname ! name of the pps 40: word $pps_sizeofname ! size of $pps_rawname 42: byte $pps_type ! type of pps (1=storage|2=stream|5=root) 43: byte $pps_uk0 ! ? 44: long $pps_prev ! previous pps 48: long $pps_next ! next pps 4c: long $pps_dir ! directory pps 50: stream 00 09 02 00 . ? 54: long 0 . ? 58: long c0 . ? 5c: stream 00 00 00 46 . ? 60: long 0 . ? 64: long $pps_ts1s ! timestamp 1 : "seconds" creation time 68: long $pps_ts1d ! timestamp 1 : "days" 6c: long $pps_ts2s ! timestamp 2 : "seconds" modified time 70: long $pps_ts2d ! timestamp 2 : "days" 74: long $pps_sb ! starting block of property 78: long $pps_size ! size of property 7c: long . ?
-
com.geekhub.lessons.lesson7.storage.Storage
Every implementation of Storage should allow save, update, delete and retrieve entities {@link com.geekhub.lessons.lesson7.objects.Entity}.
-
com.google.api.services.storage.Storage
-
com.google.code.gwt.storage.client.Storage
-
com.google.gwt.storage.client.Storage
-
com.griddynamics.java.benchmarks.model.Storage
use to store groups of objects with certain id User: akondratyev Date: Dec 16, 2010 Time: 6:58:22 PM
-
com.kellerkindt.scs.internals.Storage
-
com.trustyoram.web.storage.config.Storage
Soul Love album Advert for Learn Direct Advert learn-direct.mp3
@author Yoram Halberstam
-
de.flapdoodle.embed.mongo.config.Storage
-
de.laures.cewolf.Storage
Pluggable storage. Implement this class to change the storage concept which Cewolf uses to store chart imanges and provide the implementation class name as init parameter storage for Cewolf servlet.
@author glaures
-
de.uniluebeck.itm.tcpip.Storage
-
gov.nysenate.openleg.util.Storage
Simple file backed key-value store with that supports both published and unpublished file modes. Buffers changes in memory to reduce file system access and increase performance.
@author GraylinKim
-
js.lang.builtin.Storage
The DOM Storage mechanism is a means through which string key/value pairs can be securely stored and later retrieved for use. The goal of this addition is to provide a comprehensive means through which interactive applications can be built (including advanced abilities, such as being able to work "offline" for extended periods of time).
@version 2013/10/04 11:24:39
-
lesson07.storage.Storage
Every implementation of Storage should allow save, update, delete and retrieve entities {@link lesson07.objects.Entity}.
-
lesson7.storage.Storage
Every implementation of Storage should allow save, update, delete and retrieve entities {@link lesson7.objects.Entity}.
-
mindnotes.client.storage.Storage
-
net.citizensnpcs.properties.Storage
-
net.tomp2p.storage.Storage
The storage is typically backed by multiple Java collections (HashMap, TreeMap, etc.). This map returns the map that stores the values which are present in the DHT. If you plan to do transactions (put/get), make sure you do the locking in order to not interfere with other threads that use this map. Although the storage is threadsafe, there may be concurrency issues with respect to transactions (e.g., do a get before a put). Please use {@link StorageLayer#getLockStorage()} for full locking, and {@link StorageLayer#getLockNumber160()}, {@link StorageLayer#getLockNumber320()}, {@link StorageLayer#getLockNumber480()}, {@link StorageLayer#getLockNumber640()} for fine grained locking.
@author Thomas Bocek
-
org.apache.ambari.view.pig.persistence.Storage
Object storage interface
-
org.apache.aurora.scheduler.storage.Storage
Manages scheduler storage operations providing an interface to perform atomic changes.
-
org.apache.falcon.entity.Storage
A class to encapsulate the storage for a given feed which can either be expressed as a path on the file system or a table in a catalog.
-
org.apache.hadoop.hdfs.server.common.Storage
Storage information file.
Local storage information is stored in a separate file VERSION. It contains type of the node, the storage layout version, the namespace id, and the fs state creation time.
Local storage can reside in multiple directories. Each directory should contain the same VERSION file as the others. During startup Hadoop servers (name-node and data-nodes) read their local storage information from them.
The servers hold a lock for each storage directory while they run so that other nodes were not able to startup sharing the same storage. The locks are released when the servers stop (normally or abnormally).
-
org.apache.james.mime4j.storage.Storage
Can be used to read data that has been stored by a {@link StorageProvider}.
-
org.apache.lucene.gdata.storage.Storage
A interface every storage implementation must provide to access the
Storage. It describes all access methodes needed to store, retrieve and look up data stored in the
Storage component. This interface acts as a
Facade to hide the storage implementation from the user.
This could also act as a proxy for a remote storage. It also removes any restrictions from custom storage implementations.
@author Simon Willnauer
-
org.apache.servicemix.jbi.deployer.impl.Storage
-
org.atomojo.app.Storage
@author alex
-
org.broadinstitute.gatk.engine.io.storage.Storage
An interface representing the temporary storage of data.
@author mhanna
@version 0.1
-
org.eclipse.jgit.lib.Ref.Storage
-
org.garret.perst.Storage
-
org.geotools.caching.spatialindex.Storage
Interface for cache storage options.
@source $URL$
-
org.hsqldb.lib.Storage
An interface that supports the commonly used methods of java.io.RandomAccessFile.
@author Ocke Janssen oj@openoffice.org
@version 1.9.0
@since 1.8.0
-
org.hsqldb_voltpatches.lib.Storage
An interface that supports the commonly used methods of java.io.RandomAccessFile.
@author Ocke Janssen oj@openoffice.org
@version 1.8.0
@since 1.8.0
-
org.voltdb.planner.PlanColumn.Storage