Changes between Version 2 and Version 3 of Documentation/Architecture
- Timestamp:
- 07/21/10 15:49:19 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Documentation/Architecture
v2 v3 1 1 = Unicorn Architecture Overview = #section_title 2 2 3 == Observation Sequence == 4 3 5 [[Image(Unicorn_flow_basic.png)]] 6 4 7 The basic mechanism of Unicorn is thus: after receiving a request from a user (via The Unicorn User Interface), the Unicorn Framework creates and sends a sequence of ''observation requests'' to a number of observers. 5 8 … … 9 12 10 13 == Tasks and Observations == 14 11 15 === How does the framework decide what observation request to produce? === 16 12 17 It uses ''Tasks'' such as "validation", "conformance checking" or "check for broken links". Each task is internally known by the framework as a sequence of observations, with different priorities given to different observations. If a high level priority observation returns one or more errors (e.g a well-formedness error or invalid markup), lower priority observations will not be requested, and the user will only be sent the results of the observations already processed. 18 13 19 [[Image(Unicorn_flow_tasks.png)]] 14 20 15 21 The schema above shows how the tasks result in observations for an online Web document. Unicorn can also handle Upload or Direct input of a Web document - in which case, Unicorn will attach the document to its observation requests to each observer. 22 16 23 [[Image(Unicorn_flow_tasks2.png)]] 17 24 … … 19 26 20 27 === What kind of Request does Unicorn send? === 28 21 29 All Unicorn observers are online services (on the Web). At the moment, Unicorn can send any kind of HTTP GET or POST request. 22 30 … … 27 35 28 36 === What do Observation Responses look like? === 37 29 38 Unicorn understand Observation responses made in a language specificed in the [Documentation/Observer/Response Unicorn Response Specification]. 30 39 31 40 == Templates for UI and Results display == 41 32 42 [[Image(Unicorn_flow_templates.png)]]
