Abstract: To achieve long running batch updates, a transaction aggregator layer and one or more data aggregation queues, such as a command queue, are placed between one or more clients and a database. Writes go to the database aggregator layer and are enqueued in the appropriate data aggregation queue, which may be allocated by transaction. Committing the transaction drains the queue and writes the contents of the queue in one transaction-like update to the database. By using the transaction logic in the transaction aggregator layer, transaction-like behavior may be achieved that allows both updates and transactions to scale with less impact on database servers.

Abstract: Embodiments of systems and methods are described for reducing latency during invoice generation involving credit distribution. In some implementations, references to invoice line items are sorted by supplemental charge rate and credits are applied to the invoice line items in decreasing supplemental charge rate order. An invoice is generated that includes the invoice line items and associated credits. The process of generating applying the credits is optimized to minimize latency and to provide the greatest financial benefit to the user.

Abstract: A messaging frame can be used to allow different domains to communicate in an electronic environment that are otherwise prevented from directly communicating. A messaging frame or other communication element can be configured to receive messages or communications from any frame, object, or element in the same domain as the messaging frame. The messaging frame then can switch to a target domain in order to provide the message or communication to a frame, object, or element in the target domain. The messaging frame can include an interface definition that allows only approved messages to be passed between domains, such that the risk of malicious attack is minimized.

Abstract: Disclosed are various embodiments for performing cross-domain communication using messenger frames. One or more messenger frames are dynamically generated in response to determining that a message is to be sent from a first frame in one domain to a second frame in another domain in a client. The message is sent from the first frame to the second frame by embedding the message in addresses of the messenger frames. Code executing in the first frame and code executing in the second frame are restricted from direct communication in the client.

Abstract: Disclosed are various embodiments for the mapping of behavior to data. Multiple behavior elements from a code library that are compatible with one or more data elements of a document are automatically determined according to a data contract associated with each one of the behavior elements. Each of the behavior elements is configured to consume one or more data elements and produce a network page feature according to a behavior. One or more of the behavior elements are selected automatically according to a plurality of rules, thereby producing one or more selected behavior elements. A mapping of the one or more selected behavior elements to the one or more data elements is automatically generated.

Abstract: Embodiments of systems and methods are described for reducing latency during invoice generation involving credit distribution. In some implementations, references to invoice line items are sorted by supplemental charge rate and credits are applied to the invoice line items in decreasing supplemental charge rate order. An invoice is generated that includes the invoice line items and associated credits. The process of generating applying the credits is optimized to minimize latency and to provide the greatest financial benefit to the user.

Abstract: A messaging frame can be used to allow different domains to communicate in an electronic environment that are otherwise prevented from directly communicating. A messaging frame or other communication element can be configured to receive messages or communications from any frame, object, or element in the same domain as the messaging frame. The messaging frame then can switch to a target domain in order to provide the message or communication to a frame, object, or element in the target domain. The messaging frame can include an interface definition that allows only approved messages to be passed between domains, such that the risk of malicious attack is minimized.