Probably the fastest would be a shared memory pool... but are you sure you need that speed? A lot of times, people think they need the best of something when they really only need something that is good enough.
For example, even though shared memory would probably be the fastest option, it would probably not be easy to implement across multiple systems, your server and client would always have to be on the same machine (and by default, same OS), whereas if you used something more versatile like sockets, you could have your system work across different machines (or in the same one, no difference), different operating systems, different states, and even different countries.
So, make sure that you really need all that speed. For example, a phone conversation can be transmitted over sockets with no issue, but digitized IF (if you know what that means) could only go up to certain rates efficiently over a network.
What exactly does this imply for a Native Code programmer?
Nothing really... it's not like the WinAPI is going away.
Will a traditional MFC application just work in Windows 8?
They should, accessing desktop applications is not going away. There was an article about this not too long ago stating the intent for Visual Studio to keep supporting desktop application development, which means it will keep getting supported in Windows.
Sure, no problem. I've kept an eye out for this as well since I work on desktop applications. I doubt they'll completely get rid of the traditional desktop support any time soon, if so, I'm sure Linux will have a ton of users flocking in their direction. The market for traditional desktop applications is still large for the engineering/scientific community.
You need to send the handle of the dialog to the thread because all thes window funcs come in two forms:
::SetDlgItemText(HWND, IDC_Blue, Blue);
And the Class Specific:
myDlgItem->SetDlgItemText(IDC_Blue, Blue); or
'this' is of course given for free if you are inside the actually controls class so you can write:
So, you are in a thread, NOT in the MFC class instance, so you need to pass the window handle to the thread in order to manipulate it there.
Or even better create your own messaging system so you can send a message to the main window thread from your thread so the main window thread can do all the detailed work rathert than having to code it in your worker thread.
I don't think you can cast the LHS of an expression. It should be:
SockCLeintThread* current = dynamic_cast<SockCLeintThread*>(AfxGetThread());
AfxGetThread() returns a CWinThread* by default, so you need to cast that to the actual type that will be returned when storing it in your thread pointer. If you define current as a CWinThread* then you will not be able to use it as a SockCLeintThread* anywhere following.
I have downloaded aarot.zip and trying to understand the code. Bcoz i need to implement that on embedded programming.
But the API used here is not known to me.
So can anyone help me to understand the code.
AND IF POSSIBLE
Plz help me to know source code of the functions SetDIBits and GetDIBits. How it is working.