public interface SharkMessengerClosedChannel extends SharkMessengerChannel
Modifier and Type | Method and Description |
---|---|
void |
addTrustedMessenger(java.lang.CharSequence peerID) |
java.util.Set<java.lang.CharSequence> |
getTrustedMessengers(java.lang.CharSequence peerID) |
void |
removeTrustedMessenger(java.lang.CharSequence peerID) |
void |
sendSharkMessage(byte[] content)
Sends an unencrypted and unsigned message into this channel.
|
void |
sendSharkMessage(byte[] content,
java.lang.CharSequence receiver,
boolean sign,
boolean encrypt)
That send message method variant with all options.
|
getAge, getMessages, getMessages, getName, getURI, isBronzeAge, isInternetAge, isStoneAge, setAge
void addTrustedMessenger(java.lang.CharSequence peerID) throws SharkMessengerException
peerID
- SharkMessengerException
- messengers would not be allowed on Stone age.void removeTrustedMessenger(java.lang.CharSequence peerID) throws SharkMessengerException
SharkMessengerException
java.util.Set<java.lang.CharSequence> getTrustedMessengers(java.lang.CharSequence peerID) throws SharkMessengerException
SharkMessengerException
void sendSharkMessage(byte[] content, java.lang.CharSequence receiver, boolean sign, boolean encrypt) throws SharkMessengerException, java.io.IOException
content
- Contentreceiver
- End-to-End receiver (can be null)sign
- message is to be signed or notencrypt
- message is to be encrypted - a receiver must be specified if set trueSharkMessengerException
- some logical problems like: no receiver but encryption wanted...java.io.IOException
- problems with sending message. It is mainly caused by problems with memory, e.g. SDCard.
It does not indicate any network problems, though. ASAP is an opportunistic protocol. It will look and
wait for chances to transmit that message - as soon as possible.void sendSharkMessage(byte[] content) throws SharkMessengerException, java.io.IOException
content
- SharkMessengerException
java.io.IOException