Abstract: A system includes a resource adapter module in the form of executable code by a processor, the resource adapter module to, interact with an application running on an application server by receiving calls from applications, and provide communication between the application and any JMS provider by relaying the calls to the JMS provider.

Abstract: A memory system or flash card may include a dynamic system-level process for the management of blocks in the different memory pools. There may be spare blocks available to the pools that are over provisioned to the pool which increases the efficiency of data compaction and helps reduce the average hot count for that pool and compensate for the grown defects. The block wear and grown defects in each memory pool may be tracked so that remaining spare blocks can be re-allocated.

Abstract: An application interoperation method includes: maintaining a handler table including data type information, function information and calling information associated with each application installed in a portable device; receiving input information on a menu key of the portable device, from a user, while a first application is active; extracting, in response to the receipt of the input information, at least one function information associated with data type information, which is being processed or requested by the first application, from the handler table; dynamically generating a menu including the extracted function information to provide the user with the generated menu; receiving selection information on particular function information among the provided menu, from the user; and identifying calling information associated with the selected particular function information by referring to the handler table and executing a second application based on the identified calling information.

Abstract: A method for providing audio feedback for command line interface (CLI) commands in a computing environment. Auditory notifications are generated for indicating a completion of CLI commands. The auditory notifications are configurable by user preferences.

Abstract: A system for providing audio feedback for command line interface (CLI) commands in a computing environment. Auditory notifications are generated for indicating a completion of CLI commands. The auditory notifications are configurable by user preferences.

Abstract: The present invention provides a technical solution for a unified driver used in a handheld device. An embodiment of the technical solution may comprise a unified driving method used in a handheld device, which method may comprise: determining driver types of currently installed hardware; setting a current dispatch table on the basis of the driver type and a unified dispatch table suitable for multiple hardware and driving corresponding hardware or software by calling the current dispatch table.

Abstract: A non-transient computer-readable storage medium that stores computer program code is provided. When this code is loaded into a computer system and executed thereon, it causes the computer to compile an interface definition language (IDL) configured to provide a custom inter-orb protocol (custom IOP), configure a message header for a message in accordance with to a specification in the IDL for at least a custom-IOP message header, and define a custom-IOP message header to replace the corresponding Common Object Resource Broker Architecture (CORBA) General Inter-Orb (GIOP) message header, wherein the custom-IOP message header requires fewer bits overall than the corresponding GIOP message header by changing or eliminating at least a portion of the fields in the corresponding GIOP message header.

Abstract: A method, apparatus, system, article of manufacture, and computer readable storage medium provides the ability to dynamically bind a native assembly from a managed assembly. A managed assembly (e.g., a dynamically linked library (DLL)) is obtained. In the managed assembly, native application program interface entry points are identified. For each of the entry points, intended platform(s) and associated correct native assembly(ies) are specified in the managed assembly. The managed assembly is deployed onto a computer. For example, the single collection of managed and native assemblies can be deployed to all targeted computers, which consist of varying platform environments. During runtime execution, the executing platform of the application is determined. Based on the executing platform, an intended platform is selected and the entry points are bound to the correct native assembly.

Abstract: A first feature (e.g., chart or table) includes a reference to a dynamic pointer. Independently, the pointer is defined to point to a second feature (e.g., a query). The first feature is automatically updated to reflect a current value of the second feature. The reference to the pointer and pointer definition are recorded in a central registry, and changes to the pointer or second feature automatically cause the first feature to be updated to reflect the change. A mapping between features can be generated using the registry and can identify interrelationships to a developer. Further, changes in the registry can be tracked, such that a developer can view changes pertaining to a particular time period and/or feature of interest (e.g., corresponding to an operation problem).

Abstract: Systems, devices, and methods for using an application program interface (API) client controller to build a model view include a requestor, an executor, a converter, and one or more web APIs. Developers can create web pages that are a collection of references to API queries. The requestor maps an API path to an API request or an API call. The executor executes the API request to an API to retrieve content data. The converter then converts the retrieved content data returned by the API request to a data structure. The retrieved content data (structure) can be stored in a memory device. Multiple content data structures may be requested and stored. The data structure or data structures are then inserted in a web page template to create a model view.

Abstract: A parallel computer includes nodes, each having main memory and a messaging unit (MU). Each MU includes computer memory, which in turn includes, MU message buffers. Each MU message buffer is associated with an uninitialized process on the compute node. In the parallel computer, managing internode data communications for an uninitialized process includes: receiving, by an MU of a compute node, one or more data communications messages in an MU message buffer associated with an uninitialized process on the compute node; determining, by an application agent, that the MU message buffer associated with the uninitialized process is full prior to initialization of the uninitialized process; establishing, by the application agent, a temporary message buffer for the uninitialized process in main computer memory; and moving, by the application agent, data communications messages from the MU message buffer associated with the uninitialized process to the temporary message buffer in main computer memory.

Abstract: A parallel computer includes nodes, each having main memory and a messaging unit (MU). Each MU includes computer memory, which in turn includes, MU message buffers. Each MU message buffer is associated with an uninitialized process on the compute node. In the parallel computer, managing internode data communications for an uninitialized process includes: receiving, by an MU of a compute node, one or more data communications messages in an MU message buffer associated with an uninitialized process on the compute node; determining, by an application agent, that the MU message buffer associated with the uninitialized process is full prior to initialization of the uninitialized process; establishing, by the application agent, a temporary message buffer for the uninitialized process in main computer memory; and moving, by the application agent, data communications messages from the MU message buffer associated with the uninitialized process to the temporary message buffer in main computer memory.

Abstract: The present invention provides a technical solution for a unified driver used in a handheld device. An embodiment of the technical solution may comprise a unified driving method used in a handheld device, which method may comprise: determining driver types of currently installed hardware; setting a current dispatch table on the basis of the driver type and a unified dispatch table suitable for multiple hardware and driving corresponding hardware or software by calling the current dispatch table.

Abstract: A computer event is detected and a notification is displayed. If a dialog box corresponding to the computer event triggered the event detection, then the dialog box is modified to include further details of the event and an assistance control that links to a search engine Web page. If a dialog box did not trigger the event detection, then a dialog box is displayed with the event details and assistance control. Upon selection of the assistance control, the search engine Web page is displayed with event details pre-populated in the search term field. Targeted advertisements are displayed according to bidding on a unique descriptor associated with the specific computer event.

Abstract: An application interoperation method includes: maintaining a handler table including data type information, function information and calling information associated with each application installed in a portable device; receiving input information on a menu key of the portable device, from a user, while a first application is active; extracting, in response to the receipt of the input information, at least one function information associated with data type information, which is being processed or requested by the first application, from the handler table; dynamically generating a menu including the extracted function information to provide the user with the generated menu; receiving selection information on particular function information among the provided menu, from the user; and identifying calling information associated with the selected particular function information by referring to the handler table and executing a second application on the basis of the identified calling information.

Abstract: In a multiprocessor system with a plurality of Operating Systems (OSs) running thereon, each of the plurality of OSs has a device driver which accesses devices for shared use among the OSs. Each device driver has a task interface part which performs inter-Operating System communication at the Operating System (OS) kernel layer. A first device driver on one of the plurality of OSs includes a device interface part which accesses a device to be operated by a second device driver on a second one of the plurality of OSs. The task interface part of the second device driver receives a device access request from a task running on the second one of the plurality of OSs, adds processing request data to a request queue list of the first device driver, and returns a device access result to the task upon receipt of a notification from the device interface part.

Abstract: Internode data communications in a parallel computer that includes compute nodes that each include main memory and a messaging unit, the messaging unit including computer memory and coupling compute nodes for data communications, in which, for each compute node at compute node boot time: a messaging unit allocates, in the messaging unit's computer memory, a predefined number of message buffers, each message buffer associated with a process to be initialized on the compute node; receives, prior to initialization of a particular process on the compute node, a data communications message intended for the particular process; and stores the data communications message in the message buffer associated with the particular process. Upon initialization of the particular process, the process establishes a messaging buffer in main memory of the compute node and copies the data communications message from the message buffer of the messaging unit into the message buffer of main memory.

Abstract: Intranode data communications in a parallel computer that includes compute nodes configured to execute processes, where the data communications include: allocating, upon initialization of a first process of a compute node, a region of shared memory; establishing, by the first process, a predefined number of message buffers, each message buffer associated with a process to be initialized on the compute node; sending, to a second process on the same compute node, a data communications message without determining whether the second process has been initialized, including storing the data communications message in the message buffer of the second process; and upon initialization of the second process: retrieving, by the second process, a pointer to the second process's message buffer; and retrieving, by the second process from the second process's message buffer in dependence upon the pointer, the data communications message sent by the first process.

Abstract: A data driven, no-refresh, high-interactivity user interface framework, which can be used in (or with) web browsers to provide user interface for accessing product and service configuration through network connection. For example, the user interface can be used with web-based customer order management or product configurator. In one embodiment, the user interface presented as a web document is updated using Document Object Model (DOM) to avoid refreshing. Updates to the user interface are driven by the data managed by the user interface. An event queue for user actions to be dispatched to the server is provided to improve usability of the user interface. A user interface level application program interface is provided for external applications/modules to improve configurability.

Abstract: An efficient mechanism for terminating applications of a data processing system is described herein. In one embodiment, in response to a request for exiting from an operating environment of a data processing system, an operating system examines an operating state associated with an application running within the operating environment, where the operating state is stored at a predetermined memory location shared between the operating system and the application. The operating system immediately terminates the application if the operating state associated with the application indicates that the application is safe for a sudden termination. Otherwise, the operating system defers terminating the application if the operating state associated with the application indicates that the application is unsafe for the sudden termination.