Enhancement: Threading Model about mongoose HOT 13 CLOSED

Part 1 is implemented (to be ported on Windows still)
Part 2 (pthread join) is started.

Very nice!  Thank you.

Completed part (2).
Now, windows port left.

This almost does it.  mg_stop doesn't do anything to wait for the 
listening_loop to 
complete.  I'd suggest waiting for that thread and only then calling mg_fini 
from the 
thread that called mg_stop.

The way it works now is that mg_stop() only sets a flag and returns. Master 
thread
exits its loop, and calls mg_fini(), which waits until all threads finish. I 
don't
think that mg_stop() should block, since waiting could be long.

Perhaps an mg_wait() function that does both then?  When I'm embedding my own 
code 
into mongoose, I need to know the server has fully stopped before I can safely 
release my own resources...

Maybe a boolean flag to mg_stop() is sufficient, "to wait or not to wait" (c) ?

Perfect.

After some thinking and experimenting, I decided to leave the API unchanged.
mg_stop() now blocks unconditionally until all Mongoose threads exit.

Windows port completed.
Closing this issue.

In the latest mongoose, the "pool of threads" behavior seems to have gone away 
and I 
get a new thread to handle every request.  Is this intentional?

No, this was a breakage.
SVN head has thread pool functionality fixed. You can either update to head, or 
wait 
until 2.7 which will be released soon.