Labs/F1/Modularity: Difference between revisions

Labs/F1/Modularity (view source)

332 bytes added , 3 June 2011

668

edits

@@ Line 28: / Line 28: @@
 * WMF sends additional messages to the WebMod to fulfill the actual feature. The pattern and structure of these messages depend on the specific feature being implemented. For F1, the specifics of the API are defined below.
-Importantly, WMF is just a channel to the available WebMods. The user interface that captures the user's data and intents and passes it to WebMods via WMF is ''specific to the requested feature''. In particular, F1 continues to control the complete UI, as diagrammed above. WMF and the WebMods are headless.
+=== User Interface ===
+In the basic WebMod scenario, each WebMod is only an API provider: all UI is handled by the feature mediator, in this case F1. WMF provides a channel between this feature mediator and the various implementor/providers of the API.
+We will also consider the case of a WebMod where each provider is assigned some screen real-estate. The specifics of how the UI interactions are coordinated across the IFRAME boundary are TBD, but one aspect is clear: a WebMod with UI is a strict superset of a WebMod: authentication and authorization are still likely to require a popup to the provider's origin for trustworthiness.
 === Authentication ===