Abstract: Methods and systems are presented for facilitating migration of electronic shopping carts between devices. A user generates an electronic shopping cart based on interacting with a merchant website using a first device. In response to receiving a request for transferring the electronic shopping cart, cart data associated with the electronic shopping cart is obtained. The cart data is encoded, using a selected encoding technique, into a code, which can be a phrase, an emoji string, a QR code, or an image of a face that can be transferrable to a second device. The code is presented on the first device. In response to receiving the code from the second device, the electronic shopping cart is re-generated based on the cart data extracted from the code. The electronic shopping cart is made accessible to the user via the second device.

Abstract: Systems and methods for ingesting, managing, and distributing configuration data in one or more computing networks are provided. In examples, a flexible configuration definition framework is provided to allow for simplified ingestion, management, and distribution of configuration data to various computing devices in complex networks. Rather than table data, the framework permits expression of configuration settings in a non-relational, text-based data format to allow easy searching and filtering of configuration data and targeted distribution of data to machines and applications within the network(s).

Abstract: Examples described herein relate to standardizing content requests and responses in a content delivery network (CDN). An edge node receives a control object including sets of instructions each implementing portions of a customer's business logic. The edge node may receive, from a client, a content request identifying a content item, and may apply a set of the instructions which causes the edge node to (i) determine whether any changes are needed for the benefit of a cache server and whether any changes are need for the benefit of an origin server, and (ii) generate a processed client request identifying the content item and including, if needed, any changes for the benefit of the cache server and the origin server. The edge node transmits the processed client request to the cache server, receives a response from the cache server, and transmits a processed client response to the client.

Abstract: A cartridge assembly includes a channel and a removable assembly in releasable engagement with the channel. The removable assembly includes a cartridge body and a support plate. The cartridge body includes an engagement structure disposed adjacent a proximal end thereof. The support plate is configured to mechanically engage the cartridge body and includes an engagement structure disposed adjacent a proximal end thereof. The engagement structure of the cartridge body is configured for longitudinal alignment with the engagement structure of the support plate. The engagement structures of the cartridge body and the engagement structure of the support plate are configured to mechanically engage the engagement structure of the channel when the removable assembly is engaged with the channel.

Abstract: Examples described herein relate to systems and methods for tiered updating of configuration data. Updated configuration data is transmitted to different tiers of nodes. The nodes of a first tier are commanded to use the updated configuration data. After waiting to see if any nodes of the first tier communicate a fault after using the updated configuration data, for each of the additional tiers in the CDN it is sequentially repeated to: transmit a command to the nodes of that additional tier to use the updated configuration data; and after waiting to see if any nodes of any tier communicate a fault after using the updated configuration data, transmitting a command to the nodes of another additional tier to use the updated configuration data.

Abstract: Examples described herein relate to standardizing content requests and responses in a content delivery network (CDN). An edge node receives a control object including sets of instructions each implementing portions of a customer’s business logic. The edge node may receive, from a client, a content request identifying a content item, and may apply a set of the instructions which causes the edge node to (i) determine whether any changes are needed for the benefit of a cache server and whether any changes are need for the benefit of an origin server, and (ii) generate a processed client request identifying the content item and including, if needed, any changes for the benefit of the cache server and the origin server. The edge node transmits the processed client request to the cache server, receives a response from the cache server, and transmits a processed client response to the client.

Abstract: External customer data (ECD) may be efficiently stored in a network. When ECD is received at an edge node, the node may determine if the ECD is subject to a compiling procedure. For example, if the ECD comprises a list of entries that all have the same data type, the ECD may be placed into an array, and the array may be sorted and stored. In other examples, if the ECD received at a node includes references to other ECD, the referenced ECD may be retrieved, and the received ECD and referenced ECD may be combined and stored. In other examples, the ECD received at the node may be script instructions that can then be compiled into, and stored as, a runtime version. Any compiled ECD stored at nodes may be subject to the same invalidation and expiration policies as the uncompiled ECD from which it was derived.

Abstract: Examples described herein relate to systems and methods for tiered updating of configuration data. Updated configuration data is transmitted to different tiers of nodes. The nodes of a first tier are commanded to use the updated configuration data. After waiting to see if any nodes of the first tier communicate a fault after using the updated configuration data, for each of the additional tiers in the CDN it is sequentially repeated to: transmit a command to the nodes of that additional tier to use the updated configuration data; and after waiting to see if any nodes of any tier communicate a fault after using the updated configuration data, transmitting a command to the nodes of another additional tier to use the updated configuration data.

Abstract: Systems and methods for managing configuration changes to a network are provided. In examples, the configuration rules are received and stored in a staging directory. If the configuration rules are validated, the rules are moved to a running directory. Thereafter a request to make a change to a configuration parameter is received. The request may comprise a configuration change object, and the configuration change object may be stored in the staging directory. The configuration change object may be evaluated against the rule (and other rules of the network), and it may be moved to the running directory only after satisfying all applicable rules. In some examples, applying the rule(s) may include determining whether the configuration change exceeds a network limit on changes of a particular type with a preset time period.

Abstract: A method and apparatus for managing requests in a computer network. A request for a resource from a first node is received by a second node. The request for a resource comprises a header with a timeout indication corresponding to an amount of time the first node will wait for a response to its request for the resource. The second node sends to the first node a response to the request for the resource prior to the end of the amount of time indicated in the timeout indication. The response to the request comprises either the resource or an error message.

Abstract: Examples described herein relate to standardizing content requests and responses in a content delivery network (CDN). An edge node receives a control object including sets of instructions each implementing portions of a customer's business logic. The edge node may receive, from a client, a content request identifying a content item, and may apply a set of the instructions which causes the edge node to (i) determine whether any changes are needed for the benefit of a cache server and whether any changes are need for the benefit of an origin server, and (ii) generate a processed client request identifying the content item and including, if needed, any changes for the benefit of the cache server and the origin server. The edge node transmits the processed client request to the cache server, receives a response from the cache server, and transmits a processed client response to the client.

Abstract: Examples described herein relate to systems and methods for tiered updating of configuration data. Updated configuration data is transmitted to different tiers of nodes. The nodes of a first tier are commanded to use the updated configuration data. After waiting to see if any nodes of the first tier communicate a fault after using the updated configuration data, for each of the additional tiers in the CDN it is sequentially repeated to: transmit a command to the nodes of that additional tier to use the updated configuration data; and after waiting to see if any nodes of any tier communicate a fault after using the updated configuration data, transmitting a command to the nodes of another additional tier to use the updated configuration data.

Abstract: Examples described herein relate to standardizing content requests and responses in a content delivery network (CDN). An edge node receives a control object including sets of instructions each implementing portions of a customer's business logic. The edge node may receive, from a client, a content request identifying a content item, and may apply a set of the instructions which causes the edge node to (i) determine whether any changes are needed for the benefit of a cache server and whether any changes are need for the benefit of an origin server, and (ii) generate a processed client request identifying the content item and including, if needed, any changes for the benefit of the cache server and the origin server. The edge node transmits the processed client request to the cache server, receives a response from the cache server, and transmits a processed client response to the client.

Abstract: Examples described herein relate to systems and methods for tiered updating of configuration data. Updated configuration data is transmitted to different tiers of nodes. The nodes of a first tier are commanded to use the updated configuration data. After waiting to see if any nodes of the first tier communicate a fault after using the updated configuration data, for each of the additional tiers in the CDN it is sequentially repeated to: transmit a command to the nodes of that additional tier to use the updated configuration data; and after waiting to see if any nodes of any tier communicate a fault after using the updated configuration data, transmitting a command to the nodes of another additional tier to use the updated configuration data.

Abstract: Examples described herein relate to standardizing content requests and responses in a content delivery network (CDN). An edge node receives a control object including sets of instructions each implementing portions of a customer's business logic. The edge node may receive, from a client, a content request identifying a content item, and may apply a set of the instructions which causes the edge node to (i) determine whether any changes are needed for the benefit of a cache server and whether any changes are need for the benefit of an origin server, and (ii) generate a processed client request identifying the content item and including, if needed, any changes for the benefit of the cache server and the origin server. The edge node transmits the processed client request to the cache server, receives a response from the cache server, and transmits a processed client response to the client.

Abstract: Examples described herein relate to standardizing content requests and responses in a content delivery network (CDN). An edge node receives a control object including sets of instructions each implementing portions of a customer's business logic. The edge node may receive, from a client, a content request identifying a content item, and may apply a set of the instructions which causes the edge node to (i) determine whether any changes are needed for the benefit of a cache server and whether any changes are need for the benefit of an origin server, and (ii) generate a processed client request identifying the content item and including, if needed, any changes for the benefit of the cache server and the origin server. The edge node transmits the processed client request to the cache server, receives a response from the cache server, and transmits a processed client response to the client.

Abstract: Examples described herein relate to systems and methods for tiered updating of configuration data. Updated configuration data is transmitted to different tiers of nodes. The nodes of a first tier are commanded to use the updated configuration data. After waiting to see if any nodes of the first tier communicate a fault after using the updated configuration data, for each of the additional tiers in the CDN it is sequentially repeated to: transmit a command to the nodes of that additional tier to use the updated configuration data; and after waiting to see if any nodes of any tier communicate a fault after using the updated configuration data, transmitting a command to the nodes of another additional tier to use the updated configuration data.

Abstract: A cartridge assembly includes a channel and a removable assembly in releasable engagement with the channel. The removable assembly includes a cartridge body and a support plate. The cartridge body includes an engagement structure disposed adjacent a proximal end thereof. The support plate is configured to mechanically engage the cartridge body and includes an engagement structure disposed adjacent a proximal end thereof. The engagement structure of the cartridge body is configured for longitudinal alignment with the engagement structure of the support plate. The engagement structures of the cartridge body and the engagement structure of the support plate are configured to mechanically engage the engagement structure of the channel when the removable assembly is engaged with the channel.

Abstract: A method for identifying and mapping a maximum instantaneous stall torque capability of a fuel cell cathode valve includes: maintaining a temperature of an electric motor at a predetermined temperature, wherein the predetermined temperature is equal to or less than a freezing point of water (0° C.), and the electric motor includes motor brushes, commutator poles, a stator, a rotor rotatable with respect to the stator, and a shaft coupled to the rotor; locking the shaft of the electric motor such that the shaft is incapable of rotating, thereby fixing the shaft at a locked position; mounting the shaft of the electric motor to a dynamometer; supplying electrical energy to the electric motor; monitoring an instantaneous stall torque of the electric motor; and monitoring a rotor electrical resistance.

Abstract: Examples described herein relate to systems and methods for tiered updating of configuration data. Updated configuration data is transmitted to different tiers of nodes. The nodes of a first tier are commanded to use the updated configuration data. After waiting to see if any nodes of the first tier communicate a fault after using the updated configuration data, for each of the additional tiers in the CDN it is sequentially repeated to: transmit a command to the nodes of that additional tier to use the updated configuration data; and after waiting to see if any nodes of any tier communicate a fault after using the updated configuration data, transmitting a command to the nodes of another additional tier to use the updated configuration data.