Timeline for Applications interested to the same event and concurrency
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 18, 2021 at 9:35 | vote | accept | user3401335 | ||
| Sep 15, 2021 at 5:46 | comment | added | Martin Maat | user3401335 If there is such a strong dependency (B needing results of A), why not have A do the extended stuff in sequence? Or, have A post an event to B when it's ready. | |
| Sep 14, 2021 at 21:20 | answer | added | Diane M | timeline score: 4 | |
| Sep 14, 2021 at 21:19 | answer | added | Zach | timeline score: 3 | |
| Sep 14, 2021 at 21:16 | review | Close votes | |||
| Sep 30, 2021 at 3:02 | |||||
| Sep 14, 2021 at 21:10 | history | edited | user3401335 |
edited tags
|
|
| Sep 14, 2021 at 21:08 | comment | added | user3401335 | Hi Martin. I've rephrased the question, I hope it's more clear. The applications doesn't call directly each other. They communicate only with events on a rabbit queue. | |
| Sep 14, 2021 at 21:04 | history | edited | user3401335 | CC BY-SA 4.0 |
added 107 characters in body
|
| Sep 14, 2021 at 20:57 | comment | added | Martin Maat | It is not clear to me how this relates to .NET events. Perhaps it doesn't. It sounds like you are calling directly into application code with this and this is the problem. Try posting to a queue instead and let the receiving application deal with the message when it is ready to do so. | |
| Sep 14, 2021 at 20:36 | history | asked | user3401335 | CC BY-SA 4.0 |