Abstract: The subject disclosure is directed towards components in different server clusters, e.g., comprising software components such as components of a distributed computing system. Components are available for use by distributed computing system applications, yet managed by the distributed computing system runtime such that only a single instance can be activated and exist within communicating (non-partitioned) clusters. Also described is recovery from a situation in which no longer partitioned clusters each have created the same component.

Abstract: The subject disclosure is directed towards components in different server clusters, e.g., comprising software components such as components of a distributed computing system. Components are available for use by distributed computing system applications, yet managed by the distributed computing system runtime such that only a single instance can be activated and exist within communicating (non-partitioned) clusters. Also described is recovery from a situation in which no longer partitioned clusters each have created the same component.

Abstract: The subject disclosure is directed towards components in different server clusters, e.g., comprising software components such as components of a distributed computing system. Components are available for use by distributed computing system applications, yet managed by the distributed computing system runtime such that only a single instance can be activated and exist within communicating (non-partitioned) clusters. Also described is recovery from a situation in which no longer partitioned clusters each have created the same component.

Abstract: The subject disclosure is directed towards components in different server clusters, e.g., comprising software components such as components of a distributed computing system. Components are available for use by distributed computing system applications, yet managed by the distributed computing system runtime such that only a single instance can be activated and exist within communicating (non-partitioned) clusters. Also described is recovery from a situation in which no longer partitioned clusters each have created the same component.

Abstract: The subject disclosure is directed towards components in different server clusters, e.g., comprising software components such as components of a distributed computing system. Components are available for use by distributed computing system applications, yet managed by the distributed computing system runtime such that only a single instance can be activated and exist within communicating (non-partitioned) clusters. Also described is recovery from a situation in which no longer partitioned clusters each have created the same component.

Abstract: The subject disclosure is directed towards virtual components, e.g., comprising software components such as virtual components of a distributed computing system. Virtual components are available for use by distributed computing system applications, yet managed by the distributed computing system runtime transparent to the application with respect to automatic activation and deactivation on runtime-selected distributed computing system servers. Virtualization of virtual components is based upon mapping virtual components to their physical instantiations that are currently running, such as maintained in a global data store.

Abstract: The subject disclosure is directed towards components in different server clusters, e.g., comprising software components such as components of a distributed computing system. Components are available for use by distributed computing system applications, yet managed by the distributed computing system runtime such that only a single instance can be activated and exist within communicating (non-partitioned) clusters. Also described is recovery from a situation in which no longer partitioned clusters each have created the same component.

Abstract: The subject disclosure is directed towards virtual components, e.g., comprising software components such as virtual components of a distributed computing system. Virtual components are available for use by distributed computing system applications, yet managed by the distributed computing system runtime transparent to the application with respect to automatic activation and deactivation on runtime-selected distributed computing system servers. Virtualization of virtual components is based upon mapping virtual components to their physical instantiations that are currently running, such as maintained in a global data store.

Abstract: The deployment of multiple embedded operating system components provides a designer with flexibility when customizing an embedded operating system for a target computing device. The embedded operating system components provide extra features to expand the functionality of the target computing device. The ease with which the designer may select various embedded operating system components to deploy from an originating computing device to the target computing device simplifies the design process. Configuration data of a core embedded operating system and configuration data of the deployed embedded operating system components are merged and any conflicts between configuration data are automatically resolved without rebooting the target computing device.

Abstract: A personal information exchange module in a standardized form is used as a plug-in to a personal handheld device for information exchange such as financial transactions, facility access, medical information exchange, and the like while protecting sensitive code and data associated with the module by separating those from the operating environment of the personal handheld device. Functional capabilities of the module may also be adjusted based on available power from the personal handheld device.

Abstract: Systems and methods of payment processing via employing a payment token(s) that is supplied to smart portable devices, which are carried by customers. Such a token can be in form of a unique identifier(s) (which is generated by an issuing bank and received by the smart portable devices), and is associated with a payment amount for a merchant. Moreover, the point of sale (POS) terminal can accept the token offline, and hence a requirement for availability of communication between the POS and a payment processor/issuing bank can be mitigated.

Abstract: Systems and methods that combine coupon processing with payment processing (e.g., a credit/debit card transaction). Payment processing entities can function as the coupon clearinghouse between coupon issuers and merchants. Accordingly, processing costs can be mitigated as coupons are no longer processed separately from other tenders, (e.g., coupons can be processed same manner electronic transactions related to payments are processed, and by the same service provider.

Abstract: Systems and methods that electronically redeem coupons via an online storage component, which stores coupon data for a consumer and regardless of which issuer has issued the coupon. Such online storage medium can store coupons online (e.g., in a single location) without being tied to a particular service, and can readily provide redemption (e.g., an automatic redemption). The consumer and other retail entities (e.g., coupon issuers, merchants, and the like) can populate the online storage medium periodically, or in response to predetermined events (e.g., physical location of consumer, associated demographics, and the like.

Abstract: Systems and methods that supply associations between advertisements—and—relevance of coupons for customers. Accordingly, the customer is empowered to interact with an advertising system, and the coupons obtained are considered desirable by the customer (e.g., non-spam). The advertisement system includes a presentation component (which presents advertisement to customers); a contextualization component (which analyzes context of purchase related to the advertisement such as location, profile, and basket of the customer), and a dispenser component (which dispenses the coupons based on customer initiation—e.g., pressing a button).

Abstract: Described is a technology by which a payment abstraction layer enables application program developers to setup and/or enhance application programs to accept several payment tenders (e.g., including credit, debit, check and so forth) without requiring the application programs to implement the particular details of each payment solution provider. The payment abstraction layer provides enumeration methods and payment-related methods that are called by an application program to process payment-related input data, and instantiates payment objects to communicate with payment service providers. The payment abstraction layer may further include a hierarchy of tender (payment instrument) classes in which one class encapsulates data for different types of tenders. Some payment-related methods may be independent of any tender type, whereby an application program only need call an appropriate method with tender input data regardless of its source.