Timeline for How to send messages in the order they were queued, while ensuring that client B does not have to wait until client A has received his message?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 30, 2019 at 13:21 | audit | Suggested edits | |||
| Aug 30, 2019 at 13:22 | |||||
| Aug 10, 2019 at 11:06 | comment | added | Shane Hsu | Are these all running in a process with multiple threads? Can B see data that’s not meant for it while ignoring it? (Is data confident, though running in the same process defeats the purpose anyway.) Are those consumers long-running, always waiting for job? Or are they created on-demand? | |
| Aug 9, 2019 at 19:57 | comment | added | Robert Harvey | Add a "sequence number" or time stamp to your messages and buffer them in the receiver. This will allow you to reorder them into the proper sequence. | |
| Aug 9, 2019 at 19:50 | comment | added | Pieter B | As a side comment: look at how tcp works. It may be useful for this scenario. | |
| Aug 9, 2019 at 19:14 | history | asked | AlanWakeUp | CC BY-SA 4.0 |