ATL / WTL / STL

Here is that paragraph from the msdn doc: "When bWaitAll is FALSE, this function checks the handles in the array in order starting with index 0, until one of the objects is signaled. If multiple objects become signaled, the function returns the index of the first handle in the array whose object was signaled." This means, if your first handle is very active then your WaitForMultipleObjects() has good chances to return the first handle even if there are other similarly active signaled handles at higher indexes. You may not even notice this on a strong machines but this behavior may happen only on some slower machines with less cores... Even in that case it isn't really a "BUG", its just starvation that is about as hard to debug as timing related thread-sync issues. Although the paragraph in the msdn doc is not a warning underlined with multiple red lines it is something that can cause you a lot of headaches if your app starts to misbehave just in some special hard-to-reproduce circumstances.

I wondered why you were telling me.

Ok, Thank You.

See http://social.msdn.microsoft.com/Forums/en-US/d92b654c-9b37-4577-a6a6-f2d7efd9e608/how-to-add-web-reference-in-c-vs-2010?forum=vcgeneral[^].

Quote: I understand that peer-to-peer concept of not having a server, I guess where I'm kind of stuck is how to manage each application having essentially being a client and server. Would each aspect being handled in a separate thread by the ideal method? Maybe I am miss-understanding, but I suspect that SD1208 is not understanding the phrases client and server. Does this help any: Any application on any computer can take the server role or client role. Server in TCP/IP does not refer to a "SERVER" computer that is running a "SERVER" operating system. The server application must start first. It opens a port and listens for any client application. The client connects to a port already opened by a server. Then the two applications can chat. Thanks for your time If you work with telemetry, please check this bulletin board: http://www.bkelly.ws/irig\_106/

Why all that? You can take the '+' as a icon.

If you want to use MFC, you usually have to pay for VisualStudio. I usually use the "Professional" version, it should have everything you need. Only thing that's useful that any of the other versions have that would be nice is the remote debugger, you have to get one of the other versions for that (for debugging remotely on embedded systems and/or just remote systems). It is expensive, but if you're a professional, your company should probably cover the cost. If you're a student, I believe you can get student pricing (may depend on university). If you're neither, you may have to consider using an open source alternative. There's quite a few alternative frameworks out there (wxWidgets, Qt, etc.).

[Dynamic-Link Library Redirection] "To use DLL redirection, create a redirection file for your application. The redirection file must be named as follows: App_name.local. For example, if the application name is Editor.exe, the redirection file should be named Editor.exe.local. You must install the .local file in the application directory. You must also install the DLLs in the application directory." With best wishes, Vita

Well if anything is waiting on the thread handle, it's going to wait forever (or until it times out) because the thread handle doesn't get dealt with properly, but that would only be an issue if you were waiting on the handle (or if another unsuspecting programmer waits on your thread handle). Typically the proper way of ending a thread is to have it end itself. In the case of a socket handling thread, you can have something to signal an end to the capturing process. If your thread is in a blocking recv() call, closing your socket will trigger a return. From MSDN: Quote: Like the Win32 ExitThread API, _endthreadex does not close the thread handle.

Do not know how but I understood :) i am commented some code in files: atlapp.h and atlgdi.h

sma123# wrote: Cam anyone plz give me some reference for this? Reference for what exactly? Exception handling is the same whatever your code is doing. Veni, vidi, abiit domum

Very Cool. That helps. I shall sally forth into this new arena. Thank you for taking the time to reply. Thanks for your time If you work with telemetry, please check this bulletin board: http://www.bkelly.ws/irig\_106/

Cool. I will be working that concept. Thank you for taking the time to post. Thanks for your time If you work with telemetry, please check this bulletin board: http://www.bkelly.ws/irig\_106/

Member 10415780 wrote: I have problem about it What problem? Are you using pure Win32, MFC or WTL? Where do you want to save the text? Please give proper details of what you are doing and what does not work. Veni, vidi, abiit domum