Updated Whisper Push Notifications (markdown)
parent
8f367b0b39
commit
96e87bfdc6
|
@ -4,7 +4,7 @@ It is crucial to understand what is **Whisper Notification Service** is designed
|
|||
- to augment Whisper/5 functionality, by allowing clients to subscribe to arbitrary node that has service enabled
|
||||
- once subscribed, client receives randomly generated symmetric key (`SubscriptionKey`), which is used to control subscription (say, generating chat keys).
|
||||
- using `SubscriptionKey`, new chat sessions can be initiated (yielding yet another SymKey - `ChatKey`). By sharing that key with others, you will have a common secret that can be used to trigger notifications.
|
||||
- everywhere possible, Whisper protocol itself was used. For example, discovery mechanism is nothing more but Whisper message exchanges between parties. The same goes for notification sending. The aim was to keep the Service as slim as possible
|
||||
- everywhere possible, Whisper protocol itself was used. For example, discovery mechanism is nothing more but Whisper message exchanges between parties. The same goes for notification sending. The aim was to keep the Service as slim as possible.
|
||||
|
||||
## High-Level Overview of the process
|
||||
|
||||
|
|
Loading…
Reference in New Issue