add mailserver spec and elab on sender/receiver mode

This commit is contained in:
Oskar Thoren 2019-08-29 14:41:52 +02:00
parent 2b486e4839
commit c8e9b20f5e
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
1 changed files with 6 additions and 0 deletions

View File

@ -17,10 +17,14 @@ TBD.
In the case of mobile clients which are often offline, there is a strong need to have an ability to download offline messages. By offline messages, we mean messages sent into the Whisper network and expired before being collected by the recipient. A message stays in the Whisper network for a duration specified as `TTL` (time-to-live) property. In the case of mobile clients which are often offline, there is a strong need to have an ability to download offline messages. By offline messages, we mean messages sent into the Whisper network and expired before being collected by the recipient. A message stays in the Whisper network for a duration specified as `TTL` (time-to-live) property.
See [EIP-627](https://eips.ethereum.org/EIPS/eip-627) for more detail on *Whisper Mail Server* and *Whisper Mail Client*.
## Mailserver ## Mailserver
A mailserver can either be running as a server or as a client. A mailserver can either be running as a server or as a client.
Since Whisper is a form of DHT, a mailserver only requires a specific relationship with the receiver of a message, not with the sender of a message.
### Server ### Server
<!-- TODO: This doesn't actually describe how to implement a mailserver --> <!-- TODO: This doesn't actually describe how to implement a mailserver -->
@ -63,4 +67,6 @@ In order to use a mail server, a given node needs to connect to it directly, i.e
### Denial-of-service ### Denial-of-service
Since a mailserver is delivering expired envelopes.
TBD. TBD.