Abstract: To deliver up-to-date, coherent user data to applications upon request, the disclosed technology includes systems and methods for caching data and metadata after it has been synchronously loaded—for future retrieval with a page load time close to zero milliseconds. To provide this experience, data needs to be stored as locally to a user as possible, in the cache on the local device or in an edge cache located geographically nearby, for use in responding to requests. Applications which maintain caches of API results can be notified of their invalidation, and can detect the invalidation, propagate the invalidation to any further client tiers with the appropriate derivative type mapping, and refresh their cached values so that clients need not synchronously make the API requests again—ensuring that the client has access to the most up-to-date copy of data as inexpensively as possible—in terms of bandwidth and latency.

Abstract: The technology disclosed describes systems and methods for optimizing delivery of form factor specific content for users in different environments, such as desktop computer browsers and mobile device applications. The technology further discloses systems and methods for providing support for developers whose goal is to render specific implementations of a user interface to deliver distinct user interface experiences.

Abstract: A method for improving the accuracy of an inertial navigation system (INS) by performing a synchronization procedure to align the INS to a compass-derived initial heading comprises the steps of determining a heading of minimal error for the compass and defining that heading as the initial heading; orienting the INS to align with the so-defined initial heading; synchronizing the internal navigation system to that heading; and proceeding with navigation by use of the INS. The INS may be vehicle mounted or be contained in a portable navigation unit for swimmers or other users. The heading of minimal error may be determined by placing the compass within a multi-axis Helmholz coil system and monitoring compass readings and deviation errors as a function of actual compass positions.

Abstract: Disclosed herein are antenna boards, antenna modules, antenna board fixtures, and communication devices. For example, in some embodiments, a communication device may include an integrated circuit (IC) package, an antenna patch support, and one or more antenna patches coupled to the antenna patch support by solder or an adhesive.

Abstract: Disclosed embodiments provide a tool and methodologies for increasing security, and ease-of-access for a computer to connect privately to a specific network and or series of network-based services via a network access point without additional setup or configuration operations required of a user of the computer. In accordance with at least some disclosed embodiments, a mechanism and methodologies are provided for adaptive and dynamic provisioning of network devices for private access to network-based services for computers in a real-world environment.

Abstract: To deliver up-to-date, coherent user data to applications upon request, the disclosed technology includes systems and methods for caching data and metadata after it has been synchronously loaded—for future retrieval with a page load time close to zero milliseconds. To provide this experience, data needs to be stored as locally to a user as possible, in the cache on the local device or in an edge cache located geographically nearby, for use in responding to requests. Applications which maintain caches of API results can be notified of their invalidation, and can detect the invalidation, propagate the invalidation to any further client tiers with the appropriate derivative type mapping, and refresh their cached values so that clients need not synchronously make the API requests again—ensuring that the client has access to the most up-to-date copy of data as inexpensively as possible—in terms of bandwidth and latency.

Abstract: Disclosed are examples of systems, apparatus, methods and computer program products for delegating handling of computing events of a mobile device application. For example, an identification of a computing event can be received. The computing event can have associated metadata. The computing event can be associated with a first component of a plurality of components of a first application executable on a mobile device. The plurality of components can comprise at least a native component and a web browser component. One or more rules can be applied to the metadata. Based on the application of the one or more rules to the metadata, a second component can be identified for handling the event. Handling of the event can be delegated to the second component.

Abstract: To deliver up-to-date, coherent user data to applications upon request, the disclosed technology includes systems and methods for caching data and metadata after it has been synchronously loaded—for future retrieval with a page load time close to zero milliseconds. To provide this experience, data needs to be stored as locally to a user as possible, in the cache on the local device or in an edge cache located geographically nearby, for use in responding to requests. Applications which maintain caches of API results can be notified of their invalidation, and can detect the invalidation, propagate the invalidation to any further client tiers with the appropriate derivative type mapping, and refresh their cached values so that clients need not synchronously make the API requests again—ensuring that the client has access to the most up-to-date copy of data as inexpensively as possible—in terms of bandwidth and latency.

Abstract: To deliver up-to-date, coherent user data to applications upon request, the disclosed technology includes systems and methods for caching data and metadata after it has been synchronously loaded—for future retrieval with a page load time close to zero milliseconds. To provide this experience, data needs to be stored as locally to a user as possible, in the cache on the local device or in an edge cache located geographically nearby, for use in responding to requests. Applications which maintain caches of API results can be notified of their invalidation, and can detect the invalidation, propagate the invalidation to any further client tiers with the appropriate derivative type mapping, and refresh their cached values so that clients need not synchronously make the API requests again—ensuring that the client has access to the most up-to-date copy of data as inexpensively as possible—in terms of bandwidth and latency.

Abstract: The invention concerns a method and apparatus for water treatment. More particularly, the invention concerns a method and apparatus for water treatment using electro coagulation. A portable water treatment apparatus comprises a water inlet, a water retention tank, an electrode cartridge, and a water outlet. The water inlet is in fluid communication with the water retention tank. The water treatment apparatus is arranged to circulate water from the retention tank, through the electrode cartridge, and back into the retention tank.

Abstract: To deliver up-to-date, coherent user data to applications upon request, the disclosed technology includes systems and methods for caching data and metadata after it has been synchronously loaded—for future retrieval with a page load time close to zero milliseconds. To provide this experience, data needs to be stored as locally to a user as possible, in the cache on the local device or in an edge cache located geographically nearby, for use in responding to requests. Applications which maintain caches of API results can be notified of their invalidation, and can detect the invalidation, propagate the invalidation to any further client tiers with the appropriate derivative type mapping, and refresh their cached values so that clients need not synchronously make the API requests again—ensuring that the client has access to the most up-to-date copy of data as inexpensively as possible—in terms of bandwidth and latency.

Abstract: Producing a Ni superalloy component in which the superalloy has a ? phase matrix containing intermetallic ?? precipitates. Providing a Ni superalloy casting of the component; solutioning the component by heat treating the casting under vacuum and/or in an inert atmosphere at a temperature above the ?? solvus to homogenize the ? phase; quenching and ageing the solutioned component to grow intermetallic ?? precipitates in the homogenized ? phase. Before the solutioning step: heat treating the casting to produce a thermally grown oxide on the surface, oxide adherent to supress volatilization of Ni from the surface of the casting during the solutioning heat treatment. Performing the solutioning step under a Ni vapor pressure which is sufficient to supress volatilization of Ni from the surface of the casting during the solutioning heat treatment. During the solutioning heat treatment the component is encapsulated in a container protecting the casting from Si-doped contaminants.

Abstract: To deliver up-to-date, coherent user data to applications upon request, the disclosed technology includes systems and methods for caching data and metadata after it has been synchronously loaded—for future retrieval with a page load time close to zero milliseconds. To provide this experience, data needs to be stored as locally to a user as possible, in the cache on the local device or in an edge cache located geographically nearby, for use in responding to requests. Applications which maintain caches of API results can be notified of their invalidation, and can detect the invalidation, propagate the invalidation to any further client tiers with the appropriate derivative type mapping, and refresh their cached values so that clients need not synchronously make the API requests again—ensuring that the client has access to the most up-to-date copy of data as inexpensively as possible—in terms of bandwidth and latency.

Abstract: To deliver up-to-date, coherent user data to applications upon request, the disclosed technology includes systems and methods for caching data and metadata after it has been synchronously loaded—for future retrieval with a page load time close to zero milliseconds. To provide this experience, data needs to be stored as locally to a user as possible, in the cache on the local device or in an edge cache located geographically nearby, for use in responding to requests. Applications which maintain caches of API results can be notified of their invalidation, and can detect the invalidation, propagate the invalidation to any further client tiers with the appropriate derivative type mapping, and refresh their cached values so that clients need not synchronously make the API requests again—ensuring that the client has access to the most up-to-date copy of data as inexpensively as possible—in terms of bandwidth and latency.

Abstract: A method and apparatus of allowing a user to dynamically select a configuration of viewable data displayed via a user's dashboard graphical user interface. The method may include selecting an order of displaying the viewable data on the graphical user interface. The method may also include executing a layout of the graphical user interface to include displaying the viewable data in a first cell portion of the layout of the graphical user interface in an order based on the selecting operation and a designated priority associated with the viewable data. The data in the dashboard graphical user interface will be populated based on the user's preferences and priority associated with the data.

Abstract: A computer implemented method, apparatus, and computer usable program code for processing data packets. A set of data fragments are received at the data processing system to form a set of received data fragments. Assembly of the set of data fragments is initiated into a data packet, and a determination as to whether the data packet is an incomplete data packet. Responsive to a determination that the data packet is an incomplete data packet, the incomplete data packet is filled with at least one character to form a final data packet. The final data packet is forwarded to the target.

Abstract: A hierarchical template framework may include lower tier templates that identify groups of software components for discrete software services. The template framework also may include upper tier templates that include one or more lower tier templates and identify software components for a prearranged group of the software services configured to support and operate with an associated category of core software functions. A software developer may build a software application from the software components identified in a selected upper tier template, lower tier templates, and any other core software components identified for the core software functions. The templates prevent the software developer from having to manually locate and test all of the software components for different software services used in a software application.

Abstract: The technology disclosed describes systems and methods for optimizing delivery of form factor specific content for users in different environments, such as desktop computer browsers and mobile device applications. The technology further discloses systems and methods for providing support for developers whose goal is to render specific implementations of a user interface to deliver distinct user interface experiences.

Abstract: Herein is disclosed an in-situ system for automatically washing the walls of a wet well. The system includes a high pressure water pump coupled to a plurality of elongated high pressure water spray heads mounted along the walls of the wet well. The high pressure water spray heads are each coupled to the water pump via a solenoid valve which is in turn coupled to a control panel. The control panel is configured to operate the spray heads one at a time so that the wet well is washed by operating only one spray head at a time. The system uses standard municipal water line as a water source and uses inexpensive motors, pumps and fittings.

Abstract: A hierarchical template framework may include lower tier templates that identify groups of software components for discrete software services. The template framework also may include upper tier templates that include one or more lower tier templates and identify software components for a prearranged group of the software services configured to support and operate with an associated category of core software functions. A software developer may build a software application from the software components identified in a selected upper tier template, lower tier templates, and any other core software components identified for the core software functions. The templates prevent the software developer from having to manually locate and test all of the software components for different software services used in a software application.