Abstract: Disclosed are systems and methods for providing unified routing and caching logic for applications utilizing a CDN. First, the system maintains access to one or more edge servers for a CDN, with the one or more edge servers being configured to execute edge logic. The system receives code for an application in a specified application framework, with the code and/or application framework including a unified set of routing and caching logic for dynamic data to be applied to a number of caches, and with the unified set of routing and caching logic being derived from a centralized definition. For each of the caches, the system first analyzes the set of routing and caching logic to determine a subset of the routing and caching logic to be executed by the cache, and then atomically sends the determined subset of the routing and caching logic to the cache.

Abstract: Disclosed are systems and methods for enabling an application developer to define CDN behavior (e.g., caching rules) alongside an application program code and embedded in the same source code. The systems and methods can be used to define CDN or edge caching behavior using custom cache keys that go beyond simply using a URL. The custom cache keys and source code CDN behavior definitions can be used to enable a graphical user interface to specify traffic rules in a codeless interface. The described embodiments can be used for defining general traffic routing, to test different versions of the application or to otherwise present different versions of the application to end users, while preserving cache keys and caching behavior at the edge and throughout the application distribution layers.

Abstract: Disclosed are systems and methods for providing automated configuration of a content delivery network. First, the system maintains access to one or more edge servers for a CDN, with the edge servers being configured to execute edge logic. The system receives code for an application in a specified application framework recognized by the system, where the code includes a set of routing and caching logic with routing instructions and routing behaviors. The system then analyzes the set of routing and caching logic to define a set of edge routing behaviors and caching behaviors for one or more routes within the application. The system then determines at least a subset of the routing and caching behaviors that can be processed at the one or more edge servers using the edge logic.

Abstract: Intelligent dynamic preloading is described. A list of page requests is generated using a prediction model that predicts a plurality of page requests for a site or web application that are expected to be received from client devices, where at least some of the page requests include URLs and one or more other parameters that affect generation of a corresponding page. A request is simulated for each of the page requests included on the list of page requests to a caching layer to cause the caching layer to: make a request to an origin server for the site or dynamic web application, receive rendered pages from the origin server, and store the received rendered pages, such that subsequent requests received at the caching layer can be served from the already rendered pages.

Abstract: Disclosed are systems and methods for enabling an application developer to define CDN behavior (e.g., caching rules) alongside an application program code and embedded in the same source code. The systems and methods can be used to define CDN or edge caching behavior using custom cache keys that go beyond simply using a URL. The custom cache keys and source code CDN behavior definitions can be used to enable a graphical user interface to specify traffic rules in a codeless interface. The described embodiments can be used for defining general traffic routing, to test different versions of the application or to otherwise present different versions of the application to end users, while preserving cache keys and caching behavior at the edge and throughout the application distribution layers.

Abstract: Disclosed are systems and methods for enabling an application developer to define CDN behavior (e.g., caching rules) alongside an application program code and embedded in the same source code. The systems and methods can be used to define CDN or edge caching behavior using custom cache keys that go beyond simply using a URL. The custom cache keys and source code CDN behavior definitions can be used to enable a graphical user interface to specify traffic rules in a codeless interface. The described embodiments can be used for defining general traffic routing, to test different versions of the application or to otherwise present different versions of the application to end users, while preserving cache keys and caching behavior at the edge and throughout the application distribution layers.

Abstract: Disclosed are systems and methods for providing unified routing and caching logic for applications utilizing a CDN. First, the system maintains access to one or more edge servers for a CDN, with the one or more edge servers being configured to execute edge logic. The system receives code for an application in a specified application framework, with the code and/or application framework including a unified set of routing and caching logic for dynamic data to be applied to a number of caches, and with the unified set of routing and caching logic being derived from a centralized definition. For each of the caches, the system first analyzes the set of routing and caching logic to determine a subset of the routing and caching logic to be executed by the cache, and then atomically sends the determined subset of the routing and caching logic to the cache.

Abstract: Disclosed are systems and methods for providing automated configuration of a content delivery network. First, the system maintains access to one or more edge servers for a CDN, with the edge servers being configured to execute edge logic. The system receives code for an application in a specified application framework recognized by the system, where the code includes a set of routing and caching logic with routing instructions and routing behaviors. The system then analyzes the set of routing and caching logic to define a set of edge routing behaviors and caching behaviors for one or more routes within the application. The system then determines at least a subset of the routing and caching behaviors that can be processed at the one or more edge servers using the edge logic.

Abstract: Intelligent dynamic preloading is described. A list of page requests is generated using a prediction model that predicts a plurality of page requests for a site or web application that are expected to be received from client devices, where at least some of the page requests include URLs and one or more other parameters that affect generation of a corresponding page. A request is simulated for each of the page requests included on the list of page requests to a caching layer to cause the caching layer to: make a request to an origin server for the site or dynamic web application, receive rendered pages from the origin server, and store the received rendered pages, such that subsequent requests received at the caching layer can be served from the already rendered pages.

Abstract: An apparatus and process for forming material, the apparatus or process comprising at least one forming unit, each said forming unit having at least one forming opening to receive a feed of material to be formed, the at least one of said forming opening(s) comprises opposing or at least one forming surfaces, at least one of said opposing forming surfaces being dynamically controllable into a pre-determined shape or profile to impart a resultant shape or profile of a pre-determined formation upon the feed of material passing through said forming opening of a said forming unit.

Abstract: A device for attaching pontoon forms of watercraft to rigid keels. The invention utilizes an elongate member attached to the keel. The elongate member includes an arcuate form having a surface that substantially conforms a portion of the surface of the pontoon. The elongate member also includes a channel which receives a lip extending radially from the pontoon. The interference between the channel and the lip prevent the pontoon from being radially removed from the elongate member. The surface of the arcuate form may include ridges.