Our peer should send messages other than normal strings, and it should also be possible to see who has sent a message, or if someone has shared a file, what the file should be called. To do this, we need to implement a message type. This message type contains:
Data to be sent
(Optional) The name of the data
Who sent the data
To whom the data should be sent
Is the message a "one time" message?
How long the message should be available
When the message was sent
A structure can be implemented for this, which could look like this:
type Message struct {
id uint64
data bytes
dataName string
sender string
receivers []string
ot bool
ttl time.Duration
sendDate time.Time
}
dataName will probably only be relevant if you want to give the file to be sent a name.
ot ("one time") says that a message should only be opened once and should then no longer be readable
ttl identifies how long a message should be readable. After that, it should, if possible, no longer be readable by any of the receivers.
In order to be able to send such a message via the network, the readMessage and writeMessage interfaces must be adapted in the peer code.
Our peer should send messages other than normal strings, and it should also be possible to see who has sent a message, or if someone has shared a file, what the file should be called. To do this, we need to implement a message type. This message type contains:
dataNamewill probably only be relevant if you want to give the file to be sent a name.ot("one time") says that a message should only be opened once and should then no longer be readablettlidentifies how long a message should be readable. After that, it should, if possible, no longer be readable by any of the receivers.In order to be able to send such a message via the network, the readMessage and writeMessage interfaces must be adapted in the peer code.