on master help sign in
Added table of contents
f68c3f7Fang
docs/talk/architecture.md+23−1
@@ -3,6 +3,28 @@
3
3
4This document is complemented by talk's source code, but doesn't require it. Definitions of data structures, code snippets and diagrams will be provided where useful.
4This document is complemented by talk's source code, but doesn't require it. Definitions of data structures, code snippets and diagrams will be provided where useful.
5
5
6+## Table of contents
7+
8+* [Overview](#overview)
9+* [Core concepts & functionality](#core-concepts--functionality)
10+ * [Stories](#stories)
11+ * [Partners](#partners)
12+ * [Access control](#access-control)
13+ * [Federation](#federation)
14+* [Interfaces for applications](#interfaces-for-applications)
15+ * [Interactions](#interactions)
16+ * [Subscriptions](#subscriptions)
17+* [Communication between brokers](#communication-between-brokers)
18+ * [Interactions](#interactions-1)
19+ * [Subscriptions](#subscriptions-1)
20+* [Broker implementation](#broker-implementation)
21+ * [Subscriptions](#subscriptions-2)
22+ * [Reports](#reports)
23+ * [Messaging](#messaging)
24+* [The future](#the-future)
25+ * [Architectural issues](#architectural-issues)
26+ * [Features and functionality](#features-and-functionality)
27+* [Further reading](#further-reading)
6
28
7## Overview
29## Overview
8
30
@@ -14,7 +36,7 @@ This document, however, focusses on the platform. In talk's case, we refer to th
14
36
15## Core concepts & functionality
37## Core concepts & functionality
16
38
17−To begin to gain an understanding of how the broker functions, let's look at its state mold.
39+To begin to gain an understanding of how the broker functions, let's look at its state model.
18
40
19```
41```
20++ state :> broker state
42++ state :> broker state