Application Bridge

• Executive Summary
• Services Provided
• Services Needed
• Open Questions and Doubts
• Shared Data Structures
• Component-specific Errors
• Limitations

Executive Summary

The application bridge provides concrete interfaces to the target applications for sensing, patch deployment, reporting, and feedback. The component detaches the FastFix system from concrete target applications and bundles application access in a single component. The application bridge contains implementations of context system interfaces and client self-healing system interfaces that are target-application specific.

Services Provided

• Register new target application for use with FastFix
• Install the specified concrete sensor (sensing strategy) "into" a specified target application
• Install the specified actuator (e.g. supervisor/control mechanism, but could also be a script that changes config files) to the specified target application
• Apply the specified patch to the specified target application
• Request an error report from the specified target application. I.e. tell the component that the user should be asked to provide information
• Show feedback to the user of the specified target application

Services Needed

• Not yet clear

Open Questions and Doubts

• What is the difference/ relation to Application Bridge? Does the application bridge contain specific context system parts? Is the application bridge part of the context system?
• What parts of the Context System/ Application Bridge are independent from the target application and which are dependent (and have to be reimplemented for every target application)?

Shared Data Structures

• Yet we do not see data structures that the app bridge provides, but the following ones are interface datatypes:
  SensingStrategy, Actuator, Patch

Component-specific Errors

see [Component Specific Error Types]

Limitations

see [Component Limitations]