4 ms·
absolutely agree with the risk of slow clients saturating your connection limit when doing DB work with these, I'm a little shakier -- once I start a multistep
by awinter-py 7y ago
absolutely agree with the risk of slow clients saturating your connection limit
when doing DB work with these, I'm a little shakier -- once I start a multistep DB write, I probably want it to finish. Yes I can use a transaction to roll back the whole thing, but I think there are cases where rollback is wrong and I'd rather keep the write.
so while cancellation is cool, it's also a little fraught and hard to test.
- shhsshs 7y agoIn those rare cases you can choose not to propagate the same context through those operations. Only check for cancellation once the operations have all finished.