Techniques for redirecting a client device from a server to a mini-server are disclosed herein. Initially, the client device establishes a connection with the server. The server provides a landing page to the client device, where the landing page is programmed to include an element that, when selected, redirects the client device away from its connection with the server. In response to a selection of the element, the client device establishes a connection with the mini-server. The mini-server is part of a first local area network (LAN), and, as a result of switching networks, the client device is now a part of a second LAN. The two LANs are connected to one another via a network bridge. The mini-server is able to receive input from the client device and synchronize that input across other mini-servers in the first LAN in order to redundantly store the input.

A service provider network implements seamless scaling via proxy replay of session state. Upon a trigger, such as a determination to scale a server, a scaled server may be spun up and an identifier of the scaled server provided to a first (existing) server. The first server sends the identification of the second server, and session state information for each of the connections between the first server and the request router, to the request router. For each of the connections, the request router establishes a new connection between the request router and the second (scaled) server, and replays the session state information for the connection to the second server. The request router then routes traffic between each existing client connection (e.g., the same existing client connection which carried traffic delivered to the first server) and the corresponding new connection to the second server.

Systems and methods herein provide for a proxy infrastructure. In the proxy infrastructure, a network element (e.g., a supernode) is connected with a plurality of exit nodes. At one of a plurality of messenger units of the proxy infrastructure, a proxy protocol request is received directly from a client computing device. The proxy protocol request specifies a request and a target. In response the proxy protocol request, a selection is made between one between one of the plurality of exit nodes. A message with the request is sent from the messenger to the supernode connected with the selected exit node. Finally, the message is sent from the supernode to the selected exit node to forward the request to the target.

Systems and methods herein provide for a proxy infrastructure. In the proxy infrastructure, a network element (e.g., a supernode) is connected with a plurality of exit nodes. At one of a plurality of messenger units of the proxy infrastructure, a proxy protocol request is received directly from a client computing device. The proxy protocol request specifies a request and a target. In response the proxy protocol request, a selection is made between one between one of the plurality of exit nodes. A message with the request is sent from the messenger to the supernode connected with the selected exit node. Finally, the message is sent from the supernode to the selected exit node to forward the request to the target.

A system and method are provided for provisioning code snippets for programming a content delivery network. The method includes receiving a first client code snippet from a first client. The first client code snippet includes identity information of origin servers, standard responses for network requests, and configuration parameters to configure programmable content delivery nodes to respond to the one or more network requests. The method also includes publishing the first client code snippet to a snippet library, and indexing the first client code snippet in the snippet library. The method also includes receiving, from a second client, a request for a second client code snippet. The method also includes selecting a subset of client code snippets stored in the snippet library. The method also includes rendering identification information for the subset of client code snippets, and outputting a selected client code snippet from the subset of client code snippets.

A system and method are provided for provisioning code snippets for programming a content delivery network. The method includes receiving a first client code snippet from a first client. The first client code snippet includes identity information of origin servers, standard responses for network requests, and configuration parameters to configure programmable content delivery nodes to respond to the one or more network requests. The method also includes publishing the first client code snippet to a snippet library, and indexing the first client code snippet in the snippet library. The method also includes receiving, from a second client, a request for a second client code snippet. The method also includes selecting a subset of client code snippets stored in the snippet library. The method also includes rendering identification information for the subset of client code snippets, and outputting a selected client code snippet from the subset of client code snippets.

A demand response system includes a mobile application of a mobile device that is configured to initiate altering an operating condition of a network device disposed at a site using location based services. A demand response application interface module is configured to enable access between a utility company and the network device to communicate energy management information therebetween. The network device is configured to be remotely altered by each of the demand response application interface module and the mobile application separately based on the location based services and the energy management information. A method of managing a demand response system includes detecting a user being disposed away from a site, detecting energy management information from a utility company associated with the site, and initiating a reduction in energy use at the site in response to the relative location of the user and the energy management information.

A demand response system includes a mobile application of a mobile device that is configured to initiate altering an operating condition of a network device disposed at a site using location based services. A demand response application interface module is configured to enable access between a utility company and the network device to communicate energy management information therebetween. The network device is configured to be remotely altered by each of the demand response application interface module and the mobile application separately based on the location based services and the energy management information. A method of managing a demand response system includes detecting a user being disposed away from a site, detecting energy management information from a utility company associated with the site, and initiating a reduction in energy use at the site in response to the relative location of the user and the energy management information.

An embodiment of the present disclosure includes an RPC architecture that includes a central manager gateway with a client-facing side that allows for client access via web services protocols such as SOAP and REST. The central manager gateway further includes a server-facing side that can communicate with a plurality of network elements, with each network element implementing a common IDL architecture and RPC manager instance. Each of the network elements, and in particular their RPC manager instance, may communicate with other RPC manager instances to ‘learn’ the network topology for the system and maintain a topology database for purposes of exposing a naming service, e.g., a CORBA naming service. The network elements may elect one master element while the others remain as slaves. The central manager gateway may automatically locate the master network element and forward client requests to the same for servicing.

An embodiment of the present disclosure includes an RPC architecture that includes a central manager gateway with a client-facing side that allows for client access via web services protocols such as SOAP and REST. The central manager gateway further includes a server-facing side that can communicate with a plurality of network elements, with each network element implementing a common IDL architecture and RPC manager instance. Each of the network elements, and in particular their RPC manager instance, may communicate with other RPC manager instances to ‘learn’ the network topology for the system and maintain a topology database for purposes of exposing a naming service, e.g., a CORBA naming service. The network elements may elect one master element while the others remain as slaves. The central manager gateway may automatically locate the master network element and forward client requests to the same for servicing.