What happened ? where is my previous comment ???
Hmmm... how about this job in SBG ?Introduction - Beyond Kinect
Do you want to part of a team that builds the next big, game-changing entertainment and communication experiences? We are developing a cutting-edge new video and depth-sensor based technology that goes beyond anything on the market today.
This position will lead development of a V.1 game-changing technology currently under wraps at Microsoft. This is a newly created, high-visibility, high-impact role within Microsoft's Startup Business Group (SBG) specifically developed for this incubation project. This team is developing multiple products, based on this new technology that will be shipped with the XBOX and Lync/Skype divisions. A critical part of this role is the transitioning of complex, cutting-edge R&D into shipping products.
In particular, the SBG team seeks demonstrated world-class technical expertise and accomplishments in at least one or more of the following areas:
• Computer Vision, Computer Graphics, 3D Reconstruction, Multi-view Video, Image Interpolation, Field Programmable Gate Arrays (FPGAs)
• Digital Media and Entertainment, particularly video conferencing and video compression and decompression, and transmission/transport of video across large networks
• Game Development, specifically game engine development, complex game systems
Oh, conclusion: D is much better
@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 ?
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.
Actually, its really Pogo
The exported funtions in pgodb110.dll
The modules in pgodb110.dll and pgort110.dll