Abstract: An entertainment system (1) comprises a gaming server (2), a player station (3) operable by a player to display a simulation of a multi-stage accumulator game having a boxing theme, and a communication network (4) providing communication between the gaming server (2) and the player station (3). The gaming server (2) operates under stored program control to regulate the progress of the game and to determine an outcome thereof. The player places a wager on the outcome of the game, which is either a successful outcome in which the player wins a prize, and an unsuccessful outcome in which the player forfeits the wager. The prize may either be collected by the player or carried over as a wager for a succeeding stage of the multi-stage accumulator game.

Abstract: An entertainment system (1) comprises a gaming server (2), a player station (3) operable by a player to display a simulation of a multi-stage accumulator game having a boxing theme, and a communication network (4) providing communication between the gaming server (2) and the player station (3). The gaming server (2) operates under stored program control to regulate the progress of the game and to determine an outcome thereof. The player places a wager on the outcome of the game, which is either a successful outcome in which the player wins a prize, and an unsuccessful outcome in which the player forfeits the wager. The prize may either be collected by the player or carried over as a wager for a succeeding stage of the multi-stage accumulator game.

Abstract: The subject disclosure pertains to systems and methods for connecting pipeline components such as data flow pipeline components. Pipeline components are wrapped in metadata components that include the component as well as abstracted metadata in the form of input and output metadata descriptors. A connector can arbitrate metadata differences between pipeline components based on the metadata descriptors, thereby preventing upstream modifications from invalidating or breaking components downstream. Native or plug-in heuristic and/or related components can provide the functionality necessary to resolve metadata differences.

Abstract: Systems and methodologies that facilitate real time recognition of missing and/or invalid objects in a component based framework, via employing a graceful load fail over engine that can self heal a component based application that has missing or invalid references, to be properly read, validated and executed on a user's machine. Information about the various components installed on a user's machine can be stored to reference a package backed up to a persistence state, and/or dummy objects or stubs can be provided to represent the missing object, and typically assure proper validation and/or execution of loaded object models.

Abstract: When a component is to be loaded or executed, the version of the component to be loaded may be compared with available versions of the component. If an upgraded version of the component is available, the upgraded version of the component may be enabled to dynamically and deterministically update itself. The component may be an object in an object model. The upgraded version of the component may update itself by calling an update method. The component may be upgraded with minimum user intervention, dynamically as the object is loaded.

Abstract: An extensible generic command line parser may receive a list of options associated with an application and a command line to parse. A new command line option may be added to the options that can be parsed by adding the new command line option to the list of options. By receiving a modifiable list of valid options from an application, the parser is extensible, that is, instead of having to modify or recode the parser when a new option is added to the application, the new option may be added to the option file. When the parser receives the option list with the new option or options, any option in the file (including any new ones) may be automatically parsable by the parser.

Abstract: Impact analysis provides the ability to determine the objects that a particular object depends on or uses, as well as determine the objects that are dependent on or use a particular object. The term object may refer to tasks and/or object types, for example. Impact analysis is desirable for improving user productivity in large, complex documents because it facilitates determining how and where an object is used by other objects in the system, thereby potentially saving a great deal of manual work.