Abstract: Technologies for cross-device shared web resource caching include a client device and a shared cache device. The client device scans for a shared cache device in local proximity to the client device and, in response to the scan, registers with the shared cache device. After registering, the client device requests a cached web resource from the shared cache device. The shared cache device determines whether a cached web resource that matches the request is installed in a shared cache. The shared cache device may determine whether an origin of the request matches the origin of the cached web resource. If installed, the shared cache device sends a found response and the cached web resource to the client device. If not installed, the shared cache device sends a not-found response and the client device may request the web resource from a remote web server. Other embodiments are described and claimed.

Abstract: Technologies for cross-device shared web resource caching include a client device and a shared cache device. The client device scans for a shared cache device in local proximity to the client device and, in response to the scan, registers with the shared cache device. After registering, the client device requests a cached web resource from the shared cache device. The shared cache device determines whether a cached web resource that matches the request is installed in a shared cache. The shared cache device may determine whether an origin of the request matches the origin of the cached web resource. If installed, the shared cache device sends a found response and the cached web resource to the client device. If not installed, the shared cache device sends a not-found response and the client device may request the web resource from a remote web server. Other embodiments are described and claimed.

Abstract: Technologies for cross-device shared web resource caching include a client device and a shared cache device. The client device scans for a shared cache device in local proximity to the client device and, in response to the scan, registers with the shared cache device. After registering, the client device requests a cached web resource from the shared cache device. The shared cache device determines whether a cached web resource that matches the request is installed in a shared cache. The shared cache device may determine whether an origin of the request matches the mi gin of the cached web resource. If installed, the shared cache device sends a found response and the cached web resource to the client device. If not installed, the shared cache device sends a not-found response and the client device may request the web resource from a remote web server. Other embodiments are described and claimed.

Abstract: Technologies for cross-device shared web resource caching include a client device and a shared cache device. The client device scans for a shared cache device in local proximity to the client device and, in response to the scan, registers with the shared cache device. After registering, the client device requests a cached web resource from the shared cache device. The shared cache device determines whether a cached web resource that matches the request is installed in a shared cache. The shared cache device may determine whether an origin of the request matches the mi gin of the cached web resource. If installed, the shared cache device sends a found response and the cached web resource to the client device. If not installed, the shared cache device sends a not-found response and the client device may request the web resource from a remote web server. Other embodiments are described and claimed.

Abstract: Technologies are presented that allow application events to be recorded and replayed in a reliable and deterministic manner. A computing system may include a memory and a processor communicatively coupled with the memory. The processor may execute application logic of an application, record events associated with the application based on invocation of functions associated with the events, and store the recorded events in the memory for future playback. Recorded events may include, for example, user interactions, timing events, network downloads, callbacks, web worker tasks, etc. The recording of the events may include recording top-level functions of each event according to their order, and recording associated data including function parameters and/or return values. The recorded events may be replayed in order using the recorded associated data while suppressing non-recorded events.

Abstract: Technologies for cross-device shared web resource caching include a client device (102a) and a shared cache device (102b). The client device (102a) scans for a shared cache device (102b) in local proximity to the client device (102a) and, in response to the scan, registers with the shared cache device (102b). After registering, the client device (102a) requests a cached web resource from the shared cache device (102b). The shared cache device (102b) determines whether a cached web resource that matches the request is installed in a shared cache (102b). The shared cache device (102b) may determine whether an origin of the request matches the origin of the cached web resource. If installed, the shared cache device (102b) sends a found response and the cached web resource to the client device (102a). If not installed, the shared cache device (102b) sends a not-found response and the client device (102a) may request the web resource from a remote web server. Other embodiments are described and claimed.

Abstract: Various systems and methods for analyzing WebGL applications are described herein. A system comprises a recorder service module to intercept a plurality of graphics application programming interface (API) function calls, each of the plurality of graphics API functions calls having an associated execution context; a command translator module to translate the plurality of graphics API functions calls to a set of generic API invocations; a code generator module to generate executable code from the set of generic API invocations; and a replayer service module to test the executable code.

Abstract: Technologies are presented that allow application events to be recorded and replayed in a reliable and deterministic manner. A computing system may include a memory and a processor communicatively coupled with the memory. The processor may execute application logic of an application, record events associated with the application based on invocation of functions associated with the events, and store the recorded events in the memory for future playback. Recorded events may include, for example, user interactions, timing events, network downloads, callbacks, web worker tasks, etc. The recording of the events may include recording top-level functions of each event according to their order, and recording associated data including function parameters and/or return values. The recorded events may be replayed in order using the recorded associated data while suppressing non-recorded events.