Abstract: A data processing system includes a transaction bus, a console application in communication with the transaction bus, and a view predictor subsystem in communication with the transaction bus. The transaction bus receives, from a user application executing on a client device, a call for visual information to be provided to the user application. The view predictor subsystem determines a likelihood that the visual information will be viewable within a viewport of the user application, and a plurality of respective values for a plurality of sources of the visual information are computed based on the likelihood and a respective priority for each source. The console application provides to the transaction bus the set of potential sources of the visual information, and the transaction bus selects, based on the computed values, one of the potential sources of the visual information to be the result, which is provided to the user application.

Abstract: A data processing system includes a transaction bus, a console application in communication with the transaction bus, and a view predictor subsystem in communication with the transaction bus. The transaction bus receives, from a user application executing on a client device, a call for visual information to be provided to the user application. The view predictor subsystem determines a likelihood that the visual information will be viewable within a viewport of the user application, and a plurality of respective values for a plurality of sources of the visual information are computed based on the likelihood and a respective priority for each source. The console application provides to the transaction bus the set of potential sources of the visual information, and the transaction bus selects, based on the computed values, one of the potential sources of the visual information to be the result, which is provided to the user application.

Abstract: A data processing system includes a transaction bus, a console application in communication with the transaction bus, and a view predictor subsystem in communication with the transaction bus. The transaction bus receives, from a user application executing on a client device, a call for visual information to be provided to the user application. The view predictor subsystem determines a likelihood that the visual information will be viewable within a viewport of the user application, and a plurality of respective values for a plurality of sources of the visual information are computed based on the likelihood and a respective priority for each source. The console application provides to the transaction bus the set of potential sources of the visual information, and the transaction bus selects, based on the computed values, one of the potential sources of the visual information to be the result, which is provided to the user application.

Abstract: Aspects of the subject disclosure may include, for example, providing, by a processing system, a user interface presented at a communication device of a broker for managing curated deals in electronic advertising The processing system can obtain, via the user interface, user input comprising pricing data, targeting data, margin data, and assigned buyers. The processing system can generate multiple curated deals based on combinations of prices, targets and margins derived from the pricing data, other targeting data, and other margin data, respectively. Other embodiments are disclosed.

Abstract: Aspects of the subject disclosure may include, for example, receiving an ad call associated with an ad space available in media content that is being presented at an end user device, and conducting auctions with a group of bidders that are identified based on an analysis of line items and a curated deal, where the auctions include a curated deal auction based on the curated deal in which a broker aggregates curated deal inventory across a plurality of sellers including a seller of the ad space, and where the curated deal inventory includes the ad space. Bids can be obtained from the auctions to determine a winning bid. Other embodiments are disclosed.

Abstract: A data processing system includes a transaction bus, a console application in communication with the transaction bus, and a view predictor subsystem in communication with the transaction bus. The transaction bus receives, from a user application executing on a client device, a call for visual information to be provided to the user application. The view predictor subsystem determines a likelihood that the visual information will be viewable within a viewport of the user application, and a plurality of respective values for a plurality of sources of the visual information are computed based on the likelihood and a respective priority for each source. The console application provides to the transaction bus the set of potential sources of the visual information, and the transaction bus selects, based on the computed values, one of the potential sources of the visual information to be the result, which is provided to the user application.

Abstract: A data processing system includes a transaction bus, a console application in communication with the transaction bus, and a view predictor subsystem in communication with the transaction bus. The transaction bus receives, from a user application executing on a client device, a call for visual information to be provided to the user application. The view predictor subsystem determines a likelihood that the visual information will be viewable within a viewport of the user application, and a plurality of respective values for a plurality of sources of the visual information are computed based on the likelihood and a respective priority for each source. The console application provides to the transaction bus the set of potential sources of the visual information, and the transaction bus selects, based on the computed values, one of the potential sources of the visual information to be the result, which is provided to the user application.

Abstract: A data processing system includes a transaction bus, a console application in communication with the transaction bus, and a view predictor subsystem in communication with the transaction bus. The transaction bus receives, from a user application executing on a client device, a call for visual information to be provided to the user application. The view predictor subsystem determines a likelihood that the visual information will be viewable within a viewport of the user application, and a plurality of respective values for a plurality of sources of the visual information are computed based on the likelihood and a respective priority for each source. The console application provides to the transaction bus the set of potential sources of the visual information, and the transaction bus selects, based on the computed values, one of the potential sources of the visual information to be the result, which is provided to the user application.

Abstract: The present application is directed towards invalidating (also referred to as poisoning) ASDR table entries that are determined to be inaccurate because of changes to a multi-node system. For example, when a node leaves or enters a multi-node system, the ownership of the entries in the ASDR table can change thus invalidating cached and replica entries. More specifically, the system and methods disclosed herein include searching an ASDR table for cached entries responsive to the system determining the multi-node system has changed. After finding a cached entry, the system may determine if the entry should be poisoned. The decision to poison the entry may be responsive to the creation time of the entry, the time when the change to the multi-node system occurred, and in the case of a replica, the owner of the replica's position in a replication chain relative to source of the replica.

Abstract: The present application is directed towards systems and methods of hunting for a hash table entry in a hash table distributed over a multi-node system. More specifically, when entries are created in an ASDR table, the owner node of the entry may replicate the entry onto a non-owner node. The replica can act as a backup of the ASDR table entry in the event the node leaves the multi-mode system. When the node returns to the multi-node system, the node may no longer have the most up to date ASDR table entries, and may hunt to find the existence of the value associated with the entry. Responsive to receiving a request for an entry that may be outdated on the node, the node sends a request down a replication chain for an updated copy of the ASDR table entry from one of the replicas. Responsive to receiving the replica copy of the entry, the node responds to the client's request for the entry.

Abstract: The present invention is directed towards systems and methods for load balancing by a multi-core device intermediary between clients and services. The device may establish sub-slots in each slot of the device's packet engines. The number of sub-slots may correspond to the packet engine count. Each slot may track a different number of active connections allocated to a service. The device may assign a first and second service to each packet engine in a first slot corresponding to no active connections. These services may be assigned to different sub-slots in adjacent packet engines. The device may update, responsive to allocation of a first active connection to the first service, the first service from a sub-slot in the first slot of a first packet engine, to a corresponding sub-slot in a second slot. The second slot may correspond to one active connection allocated to the first service.

Abstract: The present invention is directed towards systems and methods for load balancing by a multi-core device intermediary between clients and services. The device may establish sub-slots in each slot of the device's packet engines. The number of sub-slots may correspond to the packet engine count. Each slot may track a different number of active connections allocated to a service. The device may assign a first and second service to each packet engine in a first slot corresponding to no active connections. These services may be assigned to different sub-slots in adjacent packet engines. The device may update, responsive to allocation of a first active connection to the first service, the first service from a sub-slot in the first slot of a first packet engine, to a corresponding sub-slot in a second slot. The second slot may correspond to one active connection allocated to the first service.

Abstract: The present application is directed towards invalidating (also referred to as poisoning) ASDR table entries that are determined to be inaccurate because of changes to a multi-node system. For example, when a node leaves or enters a multi-node system, the ownership of the entries in the ASDR table can change thus invalidating cached and replica entries. More specifically, the system and methods disclosed herein include searching an ASDR table for cached entries responsive to the system determining the multi-node system has changed. After finding a cached entry, the system may determine if the entry should be poisoned. The decision to poison the entry may be responsive to the creation time of the entry, the time when the change to the multi-node system occurred, and in the case of a replica, the owner of the replica's position in a replication chain relative to source of the replica.

Abstract: The present application is directed towards systems and methods of hunting for a hash table entry in a hash table distributed over a multi-node system. More specifically, when entries are created in an ASDR table, the owner node of the entry may replicate the entry onto a non-owner node. The replica can act as a backup of the ASDR table entry in the event the node leaves the multi-mode system. When the node returns to the multi-node system, the node may no longer have the most up to date ASDR table entries, and may hunt to find the existence of the value associated with the entry. Responsive to receiving a request for an entry that may be outdated on the node, the node sends a request down a replication chain for an updated copy of the ASDR table entry from one of the replicas. Responsive to receiving the replica copy of the entry, the node responds to the client's request for the entry.