Abstract: A system for centralized status monitoring in a multidomain network. The system includes at least one processor and at least one memory device storing instructions that when executed configure the processor to perform operations. The operations include establishing connections with domains, receiving a first request from a first domain to initiate a monitoring operation, and generating a new entry in a status table stored in a first database. The operations also may include receiving a second request from the second domain to update the monitoring operation and, in response to receiving the second request, updating the new entry in the status table by modifying the status field. The operations may also include applying a monitor operation in response to receiving a third request from a monitoring engine and generating an alert comprising entries in the status table in which the status field matches the category status.

Abstract: A computer-implemented system for dynamic inventory balancing including at a processor and a memory device comprising instructions that when executed configure the processor to perform operations. The operations including receiving an inventory data feed from at least one fulfillment center, storing (in a database) a plurality of virtual bundles with associated grouping numbers and quantities—the plurality of virtual bundles having item bundles grouping two or more of a same item in the inventory data. The operations also include exposing the database to queries from a seller portal through at least one of RESTful service, a queue based system, an index, or an object table and receiving a client order, the client order comprising a bundle selection from the plurality of virtual bundles, and updating the plurality of virtual bundles by rebalancing the plurality of virtual bundles and corresponding associated quantities based on the bundle selection.

Abstract: A system for centralized status monitoring in a multidomain network. The system includes at least one processor and at least one memory device storing instructions that when executed configure the processor to perform operations. The operations include establishing connections with domains, receiving a first request from a first domain to initiate a monitoring operation, and generating a new entry in a status table stored in a first database. The operations also may include receiving a second request from the second domain to update the monitoring operation and, in response to receiving the second request, updating the new entry in the status table by modifying the status field. The operations may also include applying a monitor operation in response to receiving a third request from a monitoring engine and generating an alert comprising entries in the status table in which the status field matches the category status.

Abstract: A computer-implemented system for dynamic inventory balancing including at a processor and a memory device comprising instructions that when executed configure the processor to perform operations. The operations including receiving an inventory data feed from at least one fulfillment center, storing (in a database) a plurality of virtual bundles with associated grouping numbers and quantities—the plurality of virtual bundles having item bundles grouping two or more of a same item in the inventory data. The operations also include exposing the database to queries from a seller portal through at least one of RESTful service, a queue based system, an index, or an object table and receiving a client order, the client order comprising a bundle selection from the plurality of virtual bundles, and updating the plurality of virtual bundles by rebalancing the plurality of virtual bundles and corresponding associated quantities based on the bundle selection.

Abstract: A system for centralized status monitoring in a multidomain network. The system includes at least one processor and at least one memory device storing instructions that when executed configure the processor to perform operations. The operations include establishing connections with domains, receiving a first request from a first domain to initiate a monitoring operation, and generating a new entry in a status table stored in a first database. The operations also may include receiving a second request from the second domain to update the monitoring operation and, in response to receiving the second request, updating the new entry in the status table by modifying the status field. The operations may also include applying a monitor operation in response to receiving a third request from a monitoring engine and generating an alert comprising entries in the status table in which the status field matches the category status.

Abstract: The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

Abstract: A computer-implemented system for dynamic inventory balancing including at a processor and a memory device comprising instructions that when executed configure the processor to perform operations. The operations including receiving an inventory data feed from at least one fulfillment center, storing (in a database) a plurality of virtual bundles with associated grouping numbers and quantities—the plurality of virtual bundles having item bundles grouping two or more of a same item in the inventory data. The operations also include exposing the database to queries from a seller portal through at least one of RESTful service, a queue based system, an index, or an object table and receiving a client order, the client order comprising a bundle selection from the plurality of virtual bundles, and updating the plurality of virtual bundles by rebalancing the plurality of virtual bundles and corresponding associated quantities based on the bundle selection.

Abstract: The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

Abstract: The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

Abstract: The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

Abstract: The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

Abstract: The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

Abstract: The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

Abstract: The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

Abstract: Background tasks are managed through background task settings that allow or prevent the execution of agents associated with mobile device applications in the background of a mobile computing device. Background task management can extend the battery life of a mobile device and can be done by a user, the mobile device or a combination thereof. Agents scheduled for execution by a mobile device are executed according to the background task settings associated with the application. Background task settings can be controlled via background task control panels. Background task settings can be set on a system-wide, application or background task basis. Disabled background tasks can be enabled when the application is next launched. A user can be invited to navigate to the background task control panels when various events occur such as the battery life dropping below a threshold or the current power consumption exceeding a threshold.

Abstract: The subject disclosure is directed towards a technology by which background application code (e.g., provided by third-party developers) runs on a mobile device in a way that is constrained with respect to resource usage. A resource manager processes a resource reservation request for background code, to determine whether the requested resources meet constraint criteria for that type of background code. If the criteria are met and the resources are available, the resources are reserved, whereby the background code is ensured priority access to its reserved resources. As a result, a properly coded background application that executes within its constraints will not experience glitches or other problems (e.g., unexpected termination) and thereby provide a good user experience.

Abstract: An integrated circuit interconnect is fabricated by using a mask to form a via in an insulating layer for a conductive plug. After the plug is formed in the via, a thin (e.g., <100 nm) isolation layer is deposited over the resulting structure. An opening is created in the isolation layer by using the same mask at a different radiation exposure level to make the opening more narrow than the underlying plug. A conductive line is then formed which makes electrical contact with the plug through the opening in the isolation layer. By vertically separating and electrically isolating the conductive plug from adjacent conductive lines, the isolation layer advantageously reduces the likelihood of an undesired electrical short occurring between the conductive plug and a nearby conductive line.

Abstract: Background tasks are managed through background task settings that allow or prevent the execution of agents associated with mobile device applications in the background of a mobile computing device. Background task management can extend the battery life of a mobile device and can be done by a user, the mobile device or a combination thereof. Agents scheduled for execution by a mobile device are executed according to the background task settings associated with the application. Background task settings can be controlled via background task control panels. Background task settings can be set on a system-wide, application or background task basis. Disabled background tasks can be enabled when the application is next launched. A user can be invited to navigate to the background task control panels when various events occur such as the battery life dropping below a threshold or the current power consumption exceeding a threshold.

Abstract: Background tasks are managed through background task settings that allow or prevent the execution of agents associated with mobile device applications in the background of a mobile computing device. Background task management can extend the battery life of a mobile device and can be done by a user, the mobile device or a combination thereof. Agents scheduled for execution by a mobile device are executed according to the background task settings associated with the application. Background task settings can be controlled via background task control panels. Background task settings can be set on a system-wide, application or background task basis. Disabled background tasks can be enabled when the application is next launched. A user can be invited to navigate to the background task control panels when various events occur such as the battery life dropping below a threshold or the current power consumption exceeding a threshold.

Abstract: Background tasks are managed through background task settings that allow or prevent the execution of agents associated with mobile device applications in the background of a mobile computing device. Background task management can extend the battery life of a mobile device and can be done by a user, the mobile device or a combination thereof. Agents scheduled for execution by a mobile device are executed according to the background task settings associated with the application. Background task settings can be controlled via background task control panels. Background task settings can be set on a system-wide, application or background task basis. Disabled background tasks can be enabled when the application is next launched. A user can be invited to navigate to the background task control panels when various events occur such as the battery life dropping below a threshold or the current power consumption exceeding a threshold.