Abstract: Providing input and output for a mobile device may be provided. At a mobile device, input may be received from at least one of a plurality of remote input devices. The plurality of remote input devices may be remote from the mobile device. The mobile device may have at least one local input device. The at least one of the plurality of remote input devices may have a greater form factor than the local input device. Next, the received input may be processed. The mobile device may transmit the output to at least one of the plurality of remote output devices. The plurality of remote output devices may be remote from the mobile device. The mobile device may have at least one local output device. The at least one of the plurality of remote output devices may have a greater form factor than the local output device.

Abstract: The subject disclosure pertains to separation of conflict resolution from a synchronization system or methodology. Upon detection of a synchronization conflict, a request can be generated by a synchronization component and transmitted to a conflict resolution component that is independent and detached from one or more synchronization components. The conflict resolution component resolves the conflict, generates a resolution response, and transmits the responses back to the requesting synchronization component for implementation, among other things.

Abstract: An execution environment accommodating object-based software transparently monitors interactions with software objects to generate operational management information for managing programs executing at plural computers. Notifications are directed to a software manager in the form of events, which can additionally be provided to applications or user programs. The software manager can group the events into sets and derive various operational management metrics from them to provide an overall picture of a program's performance, including availability. A hierarchical arrangement feature facilitates gathering information for programs scattered over plural computers. An alert feature provides warnings if metrics fall outside a specified threshold. In addition, the alert feature can automatically subscribe to additional sets of events to dynamically select the information collected by the software manager.

Abstract: An execution environment accommodating object-based software transparently monitors interactions with software objects to generate operational management information for managing programs executing at plural computers. Notifications are directed to a software manager in the form of events, which can additionally be provided to applications or user programs. The software manager can group the events into sets and derive various operational management metrics from them to provide an overall picture of a program's performance, including availability. A hierarchical arrangement feature facilitates gathering information for programs scattered over plural computers. An alert feature provides warnings if metrics fall outside a specified threshold. In addition, the alert feature can automatically subscribe to additional sets of events to dynamically select the information collected by the software manager.

Abstract: An automated workflow composable action model allows composition of actions into an activity flow. Activity flows can be based on an activity model, created on an ad hoc basis, or a combination of the two. A standard set of messages and interfaces provide flexibility and uniformity so that any of a wide variety of functionality can be easily integrated into the workflow services. Actions can encapsulate the logic for sending and receiving messages. Synchronization between actions can be supported.

Abstract: An automated workflow services system can accommodate a wide variety of workflow scenarios. A composition service, a constraint service, and a tracking service can be provided to client programs. The composition service can support client-directed instantiation of actions for activity flows. Activity flows can be based on an activity model, constructed on an ad hoc basis, or a combination thereof. Actions can be added to an activity flow at execution time of the activity flow. The tracking service can track messages to and from the actions.

Abstract: An execution environment accommodating object-based software transparently monitors interactions with software objects to generate operational management information for managing programs executing at plural computers. Notifications are directed to a software manager in the form of events, which can additionally be provided to applications or user programs. The software manager can group the events into sets and derive various operational management metrics from them to provide an overall picture of a program's performance, including availability. A hierarchical arrangement feature facilitates gathering information for programs scattered over plural computers. An alert feature provides warnings if metrics fall outside a specified threshold. In addition, the alert feature can automatically subscribe to additional sets of events to dynamically select the information collected by the software manager.

Abstract: An execution environment accommodating object-based software transparently monitors interactions with software objects to generate operational management information for managing programs executing at plural computers. Notifications are directed to a software manager in the form of events, which can additionally be provided to applications or user programs. The software manager can group the events into sets and derive various operational management metrics from them to provide an overall picture of a program's performance, including availability. A hierarchical arrangement feature facilitates gathering information for programs scattered over plural computers. An alert feature provides warnings if metrics fall outside a specified threshold. In addition, the alert feature can automatically subscribe to additional sets of events to dynamically select the information collected by the software manager.

Abstract: An execution environment accommodating object-based software transparently monitors interactions with software objects to generate operational management information for managing programs executing at plural computers. Notifications are directed to a software manager in the form of events, which can additionally be provided to applications or user programs. The software manager can group the events into sets and derive various operational management metrics from them to provide an overall picture of a program's performance, including availability. A hierarchical arrangement feature facilitates gathering information for programs scattered over plural computers. An alert feature provides warnings if metrics fall outside a specified threshold. In addition, the alert feature can automatically subscribe to additional sets of events to dynamically select the information collected by the software manager.

Abstract: An automated workflow composable action model allows composition of actions into an activity flow. Activity flows can be based on an activity model, created on an ad hoc basis, or a combination of the two. A standard set of messages and interfaces provide flexibility and uniformity so that any of a wide variety of functionality can be easily integrated into the workflow services. Actions can encapsulate the logic for sending and receiving messages. Synchronization between actions can be supported.

Abstract: An automated workflow services system can accommodate a wide variety of workflow scenarios. A composition service, a constraint service, and a tracking service can be provided to client programs. The composition service can support client-directed instantiation of actions for activity flows. Activity flows can be based on an activity model, constructed on an ad hoc basis, or a combination thereof. Actions can be added to an activity flow at execution time of the activity flow. The tracking service can track messages to and from the actions.

Abstract: An automated workflow services system can provide guidance to a user via constraints. A wide variety of constraint types are supported, including constraints based on identity, action type, and the like. Relative and negative constraints can be supported. Constraints for transitive actions can also be supported. Constraints can be based on any of a variety of facts, which can be drawn from sources outside the workflow services system.

Abstract: An execution environment accommodating object-based software transparently monitors interactions with software objects to generate operational management information for managing programs executing at plural computers. Notifications are directed to a software manager in the form of events, which can additionally be provided to applications or user programs. The software manager can group the events into sets and derive various operational management metrics from them to provide an overall picture of a program's performance, including availability. A hierarchical arrangement feature facilitates gathering information for programs scattered over plural computers. An alert feature provides warnings if metrics fall outside a specified threshold. In addition, the alert feature can automatically subscribe to additional sets of events to dynamically select the information collected by the software manager.

Abstract: Workflows can be used, created, modified and saved from within the user's working environment. Workflow can be initiated by selecting actions from a menu or workflow can be triggered by actions of users. A workflow, including an in progress workflow, can be dynamically modified, for example, to fix a process that has gone awry, to change the workflow to accommodate a changing situation, or the like. An existing workflow saved as a practice may be reused or modified. A composition system builds workflows by combining workflow units within limitations imposed by a constraint system. A constraint system accesses information stored in a knowledge base to restrict the actions an initiator of an action can initiate within a particular context in the workflow or in the environment in which the workflow operates, the targets the initiator can assign a task to, and the resources with which the initiator can associated a task.