Comments

@pmsjt: Thank you, I never really looked into those shiny new APIs because, well, I need to target XP, and in a foreseeable future, so the first thing I do with a new C++ project is setting _WIN32_WINNT to 0x0501.

But actually, async timeout notification is useless in XP anyway since there is no CancelIoEx, and CancelIo can only be called in the same thread that started it. So I kinda understand why MS teams all left XP support behind, because XP stinks. but I'm not Microsoft so I still have to.

Now I still want to ask, if I use those new Vista APIs, can I start a socket (TCP/UDP) overlapped io and let the threadpool notify me if its not yet completed after a timeout ?? I mean, I know maybe I CAN do that, but maybe I need both ...Wait APIs and ...Io APIs, and set 2 callbacks, but IMHO thats too much for such a common task, can I get the notification with just ...Io APIs ?

Good.

Thread pool is my working horse for everything not in the UI. I use QueueUserWorkItem to do async work, RegisterWaitForSingleObject to do notification/timeout/timer, and I use it to do (overlapped) IO too, I wish I can use BindIoCompleionRoutine to do IO but that dont have a async timeout notification as far as I can see, so I use RegisterWaitForSingleObject with the event in OVERLAPPED instead, which works, but its kinda wierd that BindIoCompletionRoutine has such a flaw, and I wonder if using RegisterWaitForSingleObject for IO completion has any performance hit, since its TP_WAIT while BindIoCompletionRoutine uses TP_IO ? on the other hand I wish there is RegisterWaitForMultipleObjects which would be super useful.

@Charles: Anytime !

Actually, its really Pogo

The exported funtions in pgodb110.dll

PogoDbIsLocalSymbol
PogoDbAllocEntryProbeId
PogoDbAllocSimpleProbeId
PogoDbAllocValueProbeId
PogoDbClose
PogoDbCloseCallGraph
PogoDbCloseFunction
PogoDbCloseModule
PogoDbCreateGlobalStreams
PogoDbEnableThreadSafetyChecks
PogoDbFGNodeType
PogoDbFinishFunction

The modules in pgodb110.dll and pgort110.dll

See ...Src\Tools\Pogo\....

0002 F:\dd\vctools\Compiler\UTC\Src\Tools\Pogo\pogodb\objr\i386\pogodb.obj
0003 F:\dd\vctools\Compiler\UTC\Src\Tools\Pogo\pogodb\objr\i386\pogodbmt.obj
0004 F:\dd\vctools\Compiler\UTC\Src\Tools\Pogo\pogodb\objr\i386\loadui.obj
0006 F:\dd\vctools\Compiler\UTC\Src\Tools\Pogo\pogodb\objr\i386\pgodb.rso
0002 F:\dd\vctools\Compiler\UTC\Src\Tools\Pogo\irt\pgort\objr\i386\irtdll.obj
0003 F:\dd\vctools\Compiler\UTC\Src\Tools\Pogo\irt\pgort\objr\i386\pogowin32interface.obj
0004 F:\dd\vctools\Compiler\UTC\Src\Tools\Pogo\irt\pgort\objr\i386\pgort-loadui.obj
0005 F:\dd\vctools\Compiler\UTC\Src\Tools\Pogo\irt\pgort\objr\i386\pgc.obj
0007 F:\dd\vctools\Compiler\UTC\Src\Tools\Pogo\irt\pgort\objr\i386\pgort.rsoj

OK, what I meant to say was, I hope 'the reason for Mark to left WinDiv and went to Azure' is not about (the aggresiveness, etc of) Sinofsky.

Ah, bad joke.

14 hours ago, Charles wrote

There is no replacement for Mark, of course

I hope he was not drove away from WinDiv by Sinofsky.

@Charles: What about AppContainer ??

And finally you can say the word 'Jupiter' in public now ?

I've built a tool to analyse the MDIL assemblies

MDILDump : https://github.com/WalkingCat/mdildump

It's based on the docs in those patents, hope its helpful for people interested.

Oh Dan your voice doesnt sound right ....

NICE.

I requested this series in 2011, apparently

http://channel9.msdn.com/Shows/C9-GoingNative/GoingNative-1-VC-vNext-CRT-C-and-Beyond#c634499607690000000