You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+108
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,7 @@ This codebase is heavily work in progress - among the next things to do and inve
21
21
- Is it expected that a uEntity can register more than one custom topic receiving update notifications?
22
22
- Is it supposed to be possible to register remote uuris as notification topics?
23
23
- Should remote UUris be excluded from all listeners except `subscribe` and `unsubscribe`?
24
+
- Do we need update/change notifications when remote SubscriptionResponses come in?
24
25
25
26
## Getting Started
26
27
@@ -71,3 +72,110 @@ To run (and auto-build if required) the container, in the project root run
71
72
```console
72
73
docker-compose up
73
74
```
75
+
76
+
## Design
77
+
78
+
USubscription service implementation is a three-tiered design, with the following layers:
79
+
80
+
- UTransport listeners, which link USubscription service methods to a specific transport implementation
81
+
- USubscription service, which is called from the listeners and performs input validation as well as high-level business logic orchestration; it acts as a frontend for
82
+
- subscription and notification manager actors, which contain the book-keeping and core business logic around subscriptions and notifications
83
+
84
+
The overall usubscription service implementation comprises the following building blocks:
0 commit comments