Brutkey

tef
@tef@mastodon.social

fwiw, i have some long running operation on a server, which can be cancelled by the client, and i'm looking for a good way to say "and make sure to cancel this if you give up"

rather than something that only implies "you can cancel this if you want", or worse "you should cancel this"

like CancelOnError rather than CanCancel or ShouldCancel

tef
@tef@mastodon.social

the larger issue is more accurately "this is a server side resource being held open for the client and it will expire if you do nothing, and also if you do not need it, it would be nice if you told the server if possible"

and although these properties usually happen to be true at same time, i'm also working out if "things that can only expire and not be cancelled" exists in a useful sense

tef
@tef@mastodon.social

that said and done maybe CanCancel is the right one, as the client doesn't actually care what the thing is, and only really cares about "should i send a cancel if i give up" so maybe i'm overthinking it

tef
@tef@mastodon.social

people do love to over estimate the amount of mathematics in programming when a lot of it boils down to word play

Heliomass
@heliomass@mstdn.ca

@tef@mastodon.social They do tend to put a lot of emphasis on maths in computer science degrees, versus things like writing. I suspect this comes back to bite some students when it’s dissertation time.