3 ms·
Oh, the word "event" strongly implies that you can filter, reroute, multiplex, store, branch, or do whatever with them. You can't do that if you require a respo
by marcosdumay 4y ago
Oh, the word "event" strongly implies that you can filter, reroute, multiplex, store, branch, or do whatever with them. You can't do that if you require a response.
If you create an architecture where your requests need a response, you'd better not call those "events" and ignore all the event related literature. If you want events to work, you'd better architecture your software to work without responses.