big bang checkin
remove debug printf which was still lingering in the code.
verify_document_root() should only happen AFTER the options have all been gathered and processed from (defaults, config file, command line) --> first chance that's good enough is doing this check in MG_INIT0 event.

Also note that the options should be gathered so that '-r' and '-document_root' share an options[] entry; API added to convert any argument into its corresponding 'long named form': mg_get_option_long_name()
profiling the server app shows that the main wait loop is eating ore than necessary; after all, check 10 times per second is good enough to exhibit 'instantaneous' behaviour when it comes to exiting the application - because that's the only thing which will break that loop.
couple of robustness fixes and removed two chunks of code which were duplicated elsewhere to precisely the same effect.
Win32: always provide the various _WIN32_WINNT #defines (originally available in sdkddkver.h but then you'd have to have the SDK installed)
removed dead code.  TODO: we'll need to redress the / vs. \ issue anyway: plan is to only allow / (and thus convert to it) when entering the file access functions, such as mg_fopen().  It's similar to the idea that boost path classes seemed to have: always use the '/'-based unixy notation, ad only provide the '\'-based specials on explicit demand, e.g. when going to invoke open() or stat().
don't make chat server sample throw an assertion when started in the wrong directory.
jquery errors in Safari 5/Win -> updated to unminified jquery 1.7.2 to help debugging
SSL: making sure graceful close does at least the minimal required SSL_shutdown ( http://www.openssl.org/docs/ssl/SSL_set_shutdown.html#NOTES + http://www.openssl.org/docs/ssl/SSL_shutdown.html --> we don't call SSL_shutdown() a second time as that would make us block & wait for the client to complete the close, which would be a server vulnerability)
fixed crash in chat example's JavaScript due to typeof(data)=='undefined' under some circumstances.
MSVC2010 chat project: added the example site files to the project
fixed the fix for issue #229: both Content-Type _and_ Content-Length headers should only be sent when there's a body allowed. (Not so for a HTTP 304 response, for example.)
turn on DEBUG_TRACE() when compiling in debug mode in MSVC20xx - off the shelf it defines _DEBUG instead of DEBUG.
fixes to the graceful close code - which would otherwise hang indefinitely when the client didn't close the connection, due to incorrect 'w'-related logic in there. Without the rounding-up of the remaining linger time, it would become a DISgraceful close when there wasn't any reason for that (no error conditions observed which would've turned it correctly into a disgraceful close).
fixing the broken should_keep_alive() logic. Notice that first '!' in the old code (probably my fault while merging another mongoose clone?): '... && !conn->request_info.status_code != 401 && ...' -- eek!
keep_alive_timeout fixes: first of all, this should already have been set on the _listening_ socket (allegedly accept() will then transfer that setting to the connection socket, but the code already made sure it sets kepp_alive there again and we're fine with that); also should_keep_alive() already checks for this config setting, so duplicate work in the caller there has been removed.
making the linger timeout configurable...
correcting the IPv6 support code for Win32/WinSock - testing on XP64 revealed some serious flaws related to builds for platforms older than Win7/Vista.
resetting the default keep alive timeout to 5 seconds in the mongoose server -- the '0' was there for testing only.