Abstract: A system for maintaining a database. The system includes a storage unit for storing many tablets each tablet including multiple records. The tablet controller is configured to maintain the relationship between the tablet and the storage unit. The tablet controller tracks failures to access the storage unit and designates a new storage unit for each tablet based on a storage unit failure. A router is in communication with the tablet controller and configured to distribute messages from clients to the storage units thereby serving as a layer of indirection.

Abstract: A system for a distributed database implementing a dynamic mastership strategy. The system includes a multiple data centers, each having a storage unit to store a set of records. Each data center stores its own replica of the set of records and each record includes a field that indicates which data center is assigned to be the master for that record. Since each of the data centers can he geographically distributed, one record may be more efficiently edited with the master being one geographic region while another record, possibly belonging to a different user, may be more efficiently edited with the master being located in another geographic region.

Abstract: A system for storing a distributed hash table. The system includes a storage unit, a tablet controller, a router, and a transaction bank. The storage unit has a plurality of tablets forming a hash table and each of the tablets includes multiple records. The tablet controller maintains a relationship between each tablet and the storage unit. The router hashes a record's key to determine the tablet associated with each record. Further, the router distributes messages from clients to the storage units based on the tablet-storage unit relationship thereby serving as a layer of indirection. The transaction bank propagates updates made in one record to all other replicas of the record.

Abstract: A meta-data driven data access system provides a calling application access to a plurality of data sources. The system includes a client API and a broker server. The client API receives a request for attribute data from the calling application. The client API accesses attribute structures in a local meta-data bank corresponding to the requested attribute data. The client API retrieves the attribute data from local adapters where available. If the attribute structure is not contained within the local meta-data bank, the client API requests the attribute data from the broker server. The broker server also includes a local meta-data bank and local source adapters. Accordingly, the broker server accesses the local meta-data bank to identify the adapters associated with each requested piece of attribute data. The broker server then retrieves the attribute data from the adapters associated with each attribute structure.

Abstract: Rutile TiO.sub.2 pigment particles bearing coatings comprising:(a) an inner layer comprising about 0.05-1 percent by weight, based on the weight of the TiO.sub.2, of cerium radicals and about a stoichiometric amount of phosphate radicals, based on the amount of cesium radicals,(b) a second layer of about 0.1-4 percent by weight, based on the weight of the TiO.sub.2, of amorphous silica, and optionally(c) an outer layer of (1) about 0.5 to 8 percent by weight, based on the weight of the TiO.sub.2, of hydrous alumina or (2) hydrous alumina in the amount of about 0.5-8 percent, based on the weight of the TiO.sub.2, and associated therewith up to about a stoichiometric amount of phosphate radicals needed to form aluminum phosphate,the combined total weight of said coatings being about 2 to 12 percent by weight, based on the weight of the TiO.sub.2.