On 5/6/24 11:48, Michael Richardson wrote:
> Now I treat the flush as 'OpenSSL isn't interested in the result
> of the last write anymore'. I'm not sure this assumption is correct,
> but it seems to work... (Well, it could cause duplicate messages
It does not sound correct.
I
> Now I treat the flush as 'OpenSSL isn't interested in the result
> of the last write anymore'. I'm not sure this assumption is correct,
> but it seems to work... (Well, it could cause duplicate messages
It does not sound correct.
Might be true for a read.
But, for a write, I'd thin
