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
When more than one thing use the same way of communication (for example wifi comm with phone and drone) they are stealing data packets from one another. When they are receiving separately, and one thing will get data packet intended for the second thing, it just discard that packet.
The text was updated successfully, but these errors were encountered:
Think about something with recipient added with data packet (but have to be optional to make sending to one recipient more simple). It receive next packet from queue that is intended for asking thing.
JanWielgus
changed the title
Serious problem to solve
Serious problem to solve (with multiple things using the same comm way)
Jun 19, 2020
Add something like ITransceiver decorator class that could be between low-level for example StreamComm and NoQueuePacketCommunication instances and after each receiveData() method call from this decorator it will trigger previously added event, and there you can check if some data from other source has come.
Think if there is a similar solution but to enable two (or just a number of) PacketCommunication instances to use common ITransceiver instance. This could be really good.
When more than one thing use the same way of communication (for example wifi comm with phone and drone) they are stealing data packets from one another. When they are receiving separately, and one thing will get data packet intended for the second thing, it just discard that packet.
The text was updated successfully, but these errors were encountered: