WebSocket-Node VS Windows-classic-samples

Also, I should have specified, uses package from: https://github.com/theturtle32/WebSocket-Node

A WebSocket Implementation for Node.JS

https://github.com/microsoft/Windows-classic-samples/tree/main/Samples Somewhere here I saw such a crutch.

Actually, the program was developed by Microsoft as a "sample" for their DirectShow API. The source code can be found on Microsoft's GitHub account.

MS advises against .NET shell extensions, but I think it's possible. There's a C++ example in the SDK here.

https://docs.microsoft.com/en-us/windows/win32/vss/writers https://github.com/microsoft/Windows-classic-samples/tree/main/Samples/VolumeShadowCopyServiceWriter

It depends on your OS. If you're using Windows, you ask Windows to make you a window (using the Win32 API), then tell it which pixels to draw inside of it. Here's some example code.

On the second half of the page under the heading "Advanced Winsock Samples", there's a GitHub link containing different Winsock samples including IOCP (I/O Completion Ports), async sockets, and polling. Five of these samples are also listed on the MSDN page, in order from most to least performant when handling multiple sockets.

Windows Hi-DPI API actually sends the DPI to the application. So application can draw itself as sharp as it can: https://github.com/microsoft/Windows-classic-samples/blob/master/Samples/DPIAwarenessPerWindow/client/DpiAwarenessContext.cpp#L332 .

Here's an example of a Windows program that works in this fashion and just prints some text to the screen: https://github.com/microsoft/Windows-classic-samples/blob/master/Samples/Win7Samples/begin/LearnWin32/HelloWorld/cpp/main.cpp

I found some example code to clear up my confusion at: https://github.com/microsoft/Windows-classic-samples/blob/master/Samples/WinhttpWebsocket/cpp/WinhttpWebsocket.cpp