package org.javarosa.core.services.storage;

import org.javarosa.core.util.externalizable.Externalizable;

/**
 * IStorageUtility
 * 
 * Implementations of this interface provide persistent records-based storage in which records are stored
 * and retrieved using record IDs.
 * 
 * IStorageUtility can be used in two flavors: you manage the IDs, or the utility manages the IDs:
 * 
 * If you manage the IDs, the objects you are storing must implement Persistable, which provides the ID from the object
 * itself. You then use the functions read(), write(), and remove() when dealing with storage.
 * 
 * If the utility manages the IDs, your objects need only implement Externalizable. You use the functions read(), add(),
 * update(), and remove(). add() will return a new ID for the record, which you then explicitly provide to all subsequent
 * calls to update().
 * 
 * These two schemes should not be mixed within the same StorageUtility.
 * 
 */
public interface IStorageUtility {
	
	/**
	 * Read and return the record corresponding to 'id'.
	 * 
	 * @param id id of the object
	 * @return object for 'id'. null if no object is stored under that ID
	 */
	Externalizable read (int id);

	/**
	 * Read and return the raw bytes for the record corresponding to 'id'.
	 * 
	 * @param id id of the object
	 * @return raw bytes for the record. null if no record is stored under that ID
	 */
	byte[] readBytes (int id);
	
	/**
	 * Write an object to the store. Will either add a new record, or update the existing record (if one exists) for the
	 * object's ID. This function should never be used in conjunction with add() and update() within the same StorageUtility
	 * 
	 * @param p object to store
	 * @throws StorageFullException if there is not enough room to store the object
	 */
	void write (Persistable p) throws StorageFullException;
	
	/**
	 * Add a new record to the store. This function always adds a new record; it never updates an existing record. The
	 * record ID under which this record is added is allocated by the StorageUtility. If this StorageUtility stores
	 * Persistables, you should almost certainly use write() instead.
	 * 
	 * @param e object to add
	 * @return record ID for newly added object
	 * @throws StorageFullException if not enough space available
	 */
	int add (Externalizable e) throws StorageFullException;
	
	/**
	 * Update a record in the store. The record must have previously been added to the store using add(). If this
	 * StorageUtility stores Persistables, you should almost certainly use write() instead.
	 * 
	 * @param id ID of record to update
	 * @param e updated object
	 * @throws StorageFullException if not enough space available to update
	 * @throws IllegalArgumentException if no record exists for ID
	 */
	void update (int id, Externalizable e) throws StorageFullException;
	
	/**
	 * Remove record with the given ID from the store.
	 * 
	 * @param id ID of record to remove
	 * @throws IllegalArgumentException if no record with that ID exists
	 */
	void remove (int id);
	
	/**
	 * Remove object from the store
	 * 
	 * @param p object to remove
	 * @throws IllegalArgumentException if object is not in the store
	 */
	void remove (Persistable p);

	/**
	 * Return the number of records in the store
	 * 
	 * @return number of records
	 */
	int getNumRecords ();

	/**
	 * Return whether the store is empty
	 * 
	 * @return true if there are no records in the store
	 */
	boolean isEmpty ();
	
	/**
	 * Return whether a record exists in the store
	 *
	 * @param id record ID
	 * @return true if a record exists for that ID in the store
	 */
	boolean exists (int id);
	
	/**
	 * Return total size of device storage consumed by this StorageUtility
	 *
	 * @return total size (bytes)
	 */
	int getTotalSize ();
	
	/**
	 * Get the size of a record
	 * 
	 * @param id record ID
	 * @return size of that record, in bytes
	 * @throws IllegalArgumentException if no record exists for that ID
	 */
	int getRecordSize (int id);
	
	/**
	 * Close all resources associated with this StorageUtility. Any attempt to use this StorageUtility after this call will result
	 * in error. Though not strictly necessary, it is a good idea to call this when you are done with the StorageUtility, as closing
	 * may trigger clean-up in the underlying device storage (reclaiming unused space, etc.).
	 */
	void close ();	

	/**
	 * Delete the storage utility itself, along with all stored records and meta-data
	 */
	void destroy ();
	
	/**
	 * Fetch the object that acts as the synchronization lock for this StorageUtility
	 * 
	 * @return lock object
	 */
	Object getAccessLock ();
	
}


@@ -4594,24 +4594,476 @@
 destroy ();%0D
+%0A%0D%0A%09/**%0D%0A%09 * Perform any clean-up/consolidation of the StorageUtility's underlying datastructures that is too expensive to do during%0D%0A%09 * normal usage (e.g., if all the records are scattered among 10 half-empty RMSes, repack them into 5 full RMSes)%0D%0A%09 */%0D%0A%09void repack ();%0D%0A%09%0D%0A%09/**%0D%0A%09 * If the StorageUtility has been left in a corrupt/inconsistent state, restore it to a non-corrupt state, even if it results%0D%0A%09 * in data loss%0D%0A%09 */%0D%0A%09void repair ();%0D
 %0A%09%0D%0A%09/**%0D%0A%09 

add more utility functions to API