Abstract: The embodiments set forth techniques for selecting database servers to process input/output (I/O) requests. In particular, a routing server can perform the steps of (1) receiving, from a client device, a request to perform an I/O operation to a database file that corresponds to a user account, (2) referencing a configuration file to identify a group of database servers through which access to the database file can be achieved, (3) providing, to a hash function, (i) the user account, and (ii) a count of the group of database servers, to produce a hash value that corresponds to a particular database server within the group of database servers, and (4) in response to determining that the particular database server is accessible: providing the request to the particular database server.

Abstract: The embodiments set forth techniques for managing a plurality of database engines. In particular, a database server can perform the steps of (1) concurrently executing the plurality of database engines, and (2) in response to receiving a request to perform an input/output (I/O) operation to a database file of a plurality of database files: (i) selecting, among the plurality of database engines, a database engine that is available to perform the I/O operation, (ii) performing at least one operation to make the database file accessible to the database engine, and (iii) causing the database engine to perform the I/O operation to the database file.

Abstract: The embodiments set forth techniques for managing database files for a plurality of users. In particular, a database server can perform the steps of (1) receiving, from a routing server, a request to perform an input/output (I/O) operation to a database file, (2) identifying a storage server through which the database file can be accessed, (3) interfacing with the storage server to obtain an exclusive lock on the database file, and (4) in response to determining that the exclusive lock is obtained: (i) writing, to metadata associated with the database file, information associated with the database server, and (ii) performing the I/O operation to the database file.

Abstract: Apparatuses and methods for protecting buildings which are likely to fall in the path of wildfire and/or strong wind are disclosed. The apparatus comprises two main parts: the first part comprises a set of rigid poles pre-installed in the ground surrounding a building to be protected, and, the second part comprises a set of frames, each frame supporting a mesh that, when extended over the building to be protected, shields at least a portion of the building underlying the mesh from the destructive force of fire and/or strong wind. The set of frames with its corresponding meshes, when assembled together, forms a continuous protective pyramid-shaped net that covers the entire building. The set of frames and the set of rigid poles have complementary mechanical receptacles to lock with one another so that the rigid poles collectively provide ground support when the frames are deployed over the building.

Abstract: The disclosed embodiments provide a system for managing a data store. During operation, the system stores a set of pending updates to a data store in a registry. Next, the system executes an asynchronous process that applies a first subset of updates from the registry as writes to records in the data store without blocking processing of read queries of the data store. Upon completing a write by the asynchronous process at a second portion of the data store, the system updates the registry with an indication of the completed write at the second portion of the data store. During processing of a read query of the data store, the system applies a second subset of updates from the registry to a result of the read query. Finally, the system returns the result in a response to the read query.

Abstract: A bracket system includes a first bracket configured to couple a heat exchanger coil to a base of a heat exchanger via engagement of a mounting surface of the base, where the first bracket has a recessed member and a fastening tab, and a second bracket configured to couple the heat exchanger coil to a shroud of the heat exchanger via engagement of a fastener, where the second bracket has a protruding member and a protruding ridge. The recessed member is configured to receive the protruding member such that the first bracket and the second bracket are coupled to one another in a first configuration of the bracket system, and where the fastening tab is configured to receive the protruding ridge such that the first bracket and the second bracket are coupled to one another in a second configuration of the bracket system.

Abstract: Techniques are provided for dependency-aware transaction batching for data replication. A plurality of change records corresponding to a plurality of transactions is read. Inter-transaction dependency data is generated, the inter-transaction dependency data including at least one inter-transaction dependency relationship between a plurality of pending transactions. Each inter-transaction dependency relationship indicates that a first transaction is dependent on a second transaction. A batch transaction is generated based on the inter-transaction dependency data. The batch transaction includes at least one pending transaction of the plurality of pending transactions. The batch transaction is assigned to an apply process of a plurality of apply processes configured to apply batch transactions in parallel.

Abstract: Transient duplicate key violations of unique key constraints are handled during row updates. Row changes are buffered until a point is reached that those changes are safe to execute. Row changes are effectively reordered to avoid constraint violations during execution of updates. In response to receiving a constraint key violation from a server after an attempted update, a client locally stores a record containing information regarding the failed update. Later, in response to the lack of receipt of an error in response to another update to the same column of the same table, the client uses the information in this record to instruct the server to attempt to repeat a failed update that previously attempted to change the value of a row to a value that was present in a uniqueness-constrained column at the time of the failure, but is no longer present due to the successful update.

Abstract: A bracket system includes a first bracket configured to couple a heat exchanger coil to a base of a heat exchanger via engagement of a mounting surface of the base, where the first bracket has a recessed member and a fastening tab, and a second bracket configured to couple the heat exchanger coil to a shroud of the heat exchanger via engagement of a fastener, where the second bracket has a protruding member and a protruding ridge. The recessed member is configured to receive the protruding member such that the first bracket and the second bracket are coupled to one another in a first configuration of the bracket system, and where the fastening tab is configured to receive the protruding ridge such that the first bracket and the second bracket are coupled to one another in a second configuration of the bracket system.

Abstract: Techniques are provided for client and server integration for scalable replication. A replication client transmits change records to a database server over a stream. The database server determines at least one batch comprising change records for at least one transaction. The database server generates dependency data for at least one change record in a batch based on at least one constraint identifier for at least one column. The database server determines an ordered grouping of the change records based on an operation type of each change record and the dependency data of each change record, wherein change records sharing operation types are grouped together unless a division based on the dependency data is determined. The database server generates a reordered transaction comprising a plurality of reordered operations based on the ordered grouping of the change records of the particular batch.

Abstract: Techniques are provided for dependency-aware transaction batching for data replication. A plurality of change records corresponding to a plurality of transactions is read. Inter-transaction dependency data is generated, the inter-transaction dependency data including at least one inter-transaction dependency relationship between a plurality of pending transactions. Each inter-transaction dependency relationship indicates that a first transaction is dependent on a second transaction. A batch transaction is generated based on the inter-transaction dependency data. The batch transaction includes at least one pending transaction of the plurality of pending transactions. The batch transaction is assigned to an apply process of a plurality of apply processes configured to apply batch transactions in parallel.

Abstract: Techniques are provided for client and server integration for scalable replication. A replication client transmits change records to a database server over a stream. The database server determines at least one batch comprising change records for at least one transaction. The database server generates dependency data for at least one change record in a batch based on at least one constraint identifier for at least one column. The database server determines an ordered grouping of the change records based on an operation type of each change record and the dependency data of each change record, wherein change records sharing operation types are grouped together unless a division based on the dependency data is determined. The database server generates a reordered transaction comprising a plurality of reordered operations based on the ordered grouping of the change records of the particular batch.

Abstract: Transient duplicate key violations of unique key constraints are handled during row updates. Row changes are buffered until a point is reached that those changes are safe to execute. Row changes are effectively reordered to avoid constraint violations during execution of updates. In response to receiving a constraint key violation from a server after an attempted update, a client locally stores a record containing information regarding the failed update. Later, in response to the lack of receipt of an error in response to another update to the same column of the same table, the client uses the information in this record to instruct the server to attempt to repeat a failed update that previously attempted to change the value of a row to a value that was present in a uniqueness-constrained column at the time of the failure, but is no longer present due to the successful update.

Abstract: A reliable system and method is provided for approximating a required network capacity for inhomogeneous self-similar traffic sources in a multimedia packet network. A diffusion model is first constructed for the multimedia packet network, the diffusion model assuming an input process representing the traffic sources is a sum of a plurality of independent fractional Gaussian noise processes with a plurality of corresponding Hurst parameters. A predetermined Weibull function contained in the diffusion model is then approximated, and the acceptance of a new traffic source is determined based on a predetermined packet loss probability parameter contained in the diffusion model.

Abstract: A system and method for compressing data packet headers in a lossy environment comprises circuitry that initially transmits a data packet with a full header and subsequently transmits data packets with compressed headers. The compressed headers include information that details the differences between the subsequent packets and the original full packet. Accordingly, each subsequent packet has a header whose differences are based upon the original full header of the first packet. Accordingly, a base station transceiver system includes circuitry for transmitting and receiving data packets utilizing the described header compression algorithm. Similarly, a mobile terminal is formed to receive and transmit data packet headers compressed in this manner.