Abstract: A data feed engine allows a user to create a data feed without protocol and/or formatting knowledge for the data source. The data feed engine dynamically selects a connector for any one of a variety of different types of data sources. The date feed engine can then build a search command with search parameters and a data source identity based on the automatically selected data source connector. The data feed engine publishes a reference to the generated data feed definition in a catalog of data feeds. A framework that utilizes such functionality allows creation of a mashup to with a combination of data feeds from different types of data sources.

Abstract: A data feed engine allows a user to create a data feed without protocol and/or formatting knowledge for the data source. The data feed engine dynamically selects a connector for any one of a variety of different types of data sources. The date feed engine can then build a search command with search parameters and a data source identity based on the automatically selected data source connector. The data feed engine publishes a reference to the generated data feed definition in a catalog of data feeds. A framework that utilizes such functionality allows creation of a mashup to with a combination of data feeds from different types of data sources.

Abstract: Despite the availability of mashup editors, people without programming knowledge cannot easily access the data sources to create data feeds. A data feed engine allows a user to create a data feed without protocol and/or formatting knowledge for the data source. The data feed engine automatically builds a search command with search parameters and a data source identity (e.g., server name, network address, port number, etc.). The data feed engine also encodes the built search command as a data feed and publishes a link for the data feed in a data feed catalog. After publication, users can access the catalog to combine data feeds, edit data feeds, etc., and create mashups.

Abstract: A servlet for enabling communications between a client having an Atom feed reader and an Enterprise Information System (EIS). The servlet enables communications between the client and the EIS by acting as a proxy for an J2CA resource adapter deployed on an application server. The servlet receives HTTP requests from the Atom feed reader and translates those requests into appropriate adapter function calls based on the specified HTTP function and the provided key information. The servlet then invokes the appropriate functions and receives the response from the adapter. If a single object is returned by the adapter, the servlet translates the object into Atom-compliant XML and transmits it to the Atom feed reader as the response. If multiple objects are returned, the servlet generates a list of URLs which uniquely specify and identify each object returned by the adapter and provides this list to the Atom feed reader.

Abstract: A servlet for enabling communications between a client having an Atom feed reader and an Enterprise Information System (EIS). The servlet enables communications between the client and the EIS by acting as a proxy for an J2CA resource adapter deployed on an application server. The servlet receives HTTP requests from the Atom feed reader and translates those requests into appropriate adapter function calls based on the specified HTTP function and the provided key information. The servlet then invokes the appropriate functions and receives the response from the adapter. If a single object is returned by the adapter, the servlet translates the object into Atom-compliant XML and transmits it to the Atom feed reader as the response. If multiple objects are returned, the servlet generates a list of URLs which uniquely specify and identify each object returned by the adapter and provides this list to the Atom feed reader.

Abstract: Despite the availability of mashup editors, people without programming knowledge cannot easily access the data sources to create data feeds. A data feed engine allows a user to create a data feed without protocol and/or formatting knowledge for the data source. The data feed engine automatically builds a search command with search parameters and a data source identity (e.g., server name, network address, port number, etc.). The data feed engine also encodes the built search command as a data feed and publishes a link for the data feed in a data feed catalog. After publication, users can access the catalog to combine data feeds, edit data feeds, etc., and create mashups.

Abstract: A data feed engine allows a user to create a data feed without protocol and/or formatting knowledge for the data source. The data feed engine dynamically selects a connector for any one of a variety of different types of data sources. The date feed engine can then build a search command with search parameters and a data source identity based on the automatically selected data source connector. The data feed engine publishes a reference to the generated data feed definition in a catalog of data feeds. A framework that utilizes such functionality allows creation of a mashup to with a combination of data feeds from different types of data sources.

Abstract: A composition of an aqueous, an aqueous acid, and an aqueous alkaline foaming additive (“foamer”) functions in a wide pH range and under conditions of salt, alcohol, and hydrocarbon contamination. The foaming additive (“foamer”) composition includes a mixture of a salt of an alkyl ether sulfate surfactant, a polymer or combination of polymers, and either a water miscible solvent for the liquid foamer additive or a silicon compound for a substantially anhydrous foamer additive.

Abstract: A multitasking operating system permits application programs (and their developers) to influence a schedule of execution of program threads derived from the application programs. Each of the program threads is assigned a priority level and a dispatch class in which the thread resides. Based on these parameters, the operating system schedules the threads for execution in the following manner. The operating system queues the highest priority thread which is available for execution from each dispatch class onto a run list for execution by a processor. The highest priority thread on the run list is executed first. An application program thread can change the dispatch class in which another program thread resides. An executing program thread can also voluntarily yield to a specified program thread in the same dispatch class or permit the highest priority available thread in the same dispatch class to be queued on the run list with itself being available and in contention for the run list.

Abstract: A multitasking operating system permits application programs (and their developers) to influence a schedule of execution of program threads which constitute the application programs by specifying parameters for the program threads. The parameters indicate each thread's priority level and dispatch class in which the thread resides. The application programs specify the thread's parameters based on the following principles of the operating system. The operating system queues the highest priority thread available for execution from each dispatch class onto a run list for execution by a processor. The highest priority thread on the run list is executed first. While this thread is dispatchable and being executed, no other thread from the same dispatch class can preempt it unless this executing thread voluntarily relinquishes control of the processor, even if the other thread has a higher priority.

Abstract: A program loader for virtual machine (VM) operating systems (OS) for computer and data processing systems permits the loading and execution of programs in different virtual machine environments, depending on addressing and residency requirements of the programs. An improved subsystem to the VM operating system contains command language and file management capability that allows programs to be invoked via a direct branch linkage in the addressing mode of the target program, allows the program's addressing mode and residency mode to be dynamically and interactively overridden at any point in the load process, controls whether previously loaded programs remain in storage along with the program that is currently being loaded, and allows the loading and execution of programs that are architecturally dependent as well as programs that have no architecture dependencies.