Re: [libmicrohttpd] Clarification on receiving on one thread, replying on another

[Christian Grothoff]

On 10/25/2016 03:59 PM, Tom Cornell wrote:
> Hmmm. Okay. I was already returning from the access handler without 
> queuing a response (since that was happening on another thread), 
> but I am not seeing this subsequent extra call to the access handler. 
> Is that because I am suspending the connection before returning?
> (I also don't see it after resuming the connection, but since at that
> point I've queued a response in a different thread, presumably I'm 
> well into the world of Undefined Behavior at that point.)

Yes, queueing a response in a different thread may indeed give you
undefined behavior due to race conditions.

> I will rework the code along the lines you suggest. Thanks for the 
> quick reply!

Ok, if it still doesn't work, I suggest you come back with a minimal
example for us to look at -- easier to discuss with concrete code.

signature.asc
Description: OpenPGP digital signature