这篇讲得很清楚，就转过来了，原文如下：
因项目需要，最近在学习MFC,下午在一篇教程中提到了临时窗口、永久窗口，作者让读者自行查阅MSDN，了解临时窗口与永久窗口的概念，出于好奇，出于方便，直接百度一下，看到了几篇题为解释临时窗口与永久窗口的文章，随后网友在论坛中附上了MSDN中的原文，仔细翻译一下，发现网上查到的几篇文章，对这个概念的解释是有问题和不足的。
首先我要说明一点的就是窗口是没有临时与永久之分的，窗口是一种资源，随着CreateWindow的调用而产生，随着DestroyWindow的调用而被销毁(资源所占据的内存被回收)，在windows程序设计中通过句柄(这里可以将句柄看成是C++中的指针)来标识资源，通过句柄来操作窗口，控制窗口，也就是说真正表示窗口的是窗口句柄HWND类型变量，为了方便开发、提高开发效率，MFC帮我们封装了与窗口有关的操作(就是对win32 API的间接调用而已)，并将标识窗口的句柄的HWND的变量，封装到了CWnd类中，作为其数据成员，所以我们在调用MFC类中与Win32同名的成员函数的时候，就少去了句柄这一参数，是因为CWnd类维护了这一HWND类型的变量，归根结底MFC的成员函数还是调用了win32函数，说这么多的原因主要是想说明MFC 中的C++窗口对象只是我们操作窗口的一层封装，一种手段，MSDN中说的是临时窗口对象的概念，而不是临时窗口与永久窗口，因为根本就没有这两个概念（创建窗口之后，只要不直接、间接调用destroywindow那么窗口就一直占据内存资源）
如上所述，在MFC中，都是以C++对象来操作窗口，而窗口是用句柄来标识的，这样就需要将窗口和C++对象关联起来。通过C++对象的成员变量m_hWnd(HWND类型)来建立这种联系.
首先解释一下何为永久窗口对象：
在MFC中建立一个窗口的步骤：
CWnd win;
win.Create();（篇幅所限此处略去Create函数的参数，create函数负责创建窗口并将其关联到win这个对象上，说白了就是给m_hWnd这个成员变量赋值）；
此时win这个对象就是永久窗口对象，接着调用这段代码 CWnd* pWnd = CWnd::FromHandle(win.m_hWnd)返回的就是指向win这个永久窗口对象的指针，如果我们接着做如下操作：HWND hwnd = win.Detach();
接着再调用上面的代码：pWnd = CWnd::FromHandle(hwnd)，此时pWnd指向的对象就是临时窗口对象
以下是MSDN中对CWnd::FromHandle函数返回值的说明
Returns a pointer to a CWnd object when given a handle to a window. If a CWnd object is not attached to the handle, a temporary CWnd object is created and attached.
The pointer may be temporary and should not be stored for later use
对于临时窗口对象，windows程序会在线程出于空闲时间的时候(消息队列为空)，自动调用CWinThread::DeleteTempMap()函数把临时对象从他关联的窗口句柄上卸载下来，取消这种关联，并删除这个临时窗口对象，但注意，这个窗口句柄还是存在的，因为窗口这个资源并没有销毁，销毁的只是封装窗口句柄的这个临时的C++对象，所以我们不能存储这个对象的指针，在其他地方调用，因为它随时会被回收，变成无效指针，同样在不同的线程中也是不能传递C++窗口对象的，此处 不管该C++窗口对象是不是临时的，如果我们要在其它地方操作这个窗口，应该存储代表窗口的句柄，而非C++对象。
以下是MSDN原文对临时窗口对象与永久窗口对象的说明：
TN003: Mapping of Windows Handles to Objects
This note describes the MFC routines that support mapping Windows object handles to C++ objects.
The Problem
Windows objects are normally represented by HANDLEs. The MFC classes wrap Windows object handles with C++ objects. The handle wrapping functions of the MFC class library provide a way to find the C++ object that is wrapping the Windows object with a particular handle. There are times when a Windows object does not have a C++ wrapper object, however, and at these times a temporary object is created to act as the C++ wrapper.
The Windows objects that use handle maps are:
HWND (CWnd and CWnd-derived classes)
HDC (CDC and CDC-derived classes)
HMENU (CMenu)
HPEN (CGdiObject)
HBRUSH (CGdiObject)
HFONT (CGdiObject)
HBITMAP (CGdiObject)
HPALETTE (CGdiObject)
HRGN (CGdiObject)
HIMAGELIST (CImageList)
SOCKET (CSocket)
Given a handle to any of these objects, you can find the MFC object that wraps the handle by calling the static member function FromHandle. For example, given an HWND called hWnd:
CWnd::FromHandle(hWnd)
will return a pointer to the CWnd that wraps the hWnd. If that hWnd does not have a specific wrapper object, then a temporary CWnd is created to wrap the hWnd. This makes it possible to get a valid C++ object from any handle.
Once you have a wrapper object, you can get to its handle through a public member variable. In the case of an CWnd, m_hWnd contains the HWND for that object.
Attaching Handles to MFC Objects
Given a newly created handle-wrapper object and a handle to a Windows object, you can associate the two by calling Attach. For example:
CWnd myWnd;
myWnd.Attach(hWnd);
This makes an entry in the permanent map associating myWnd and hWnd. Calling CWnd::FromHandle(hWnd) will now return a pointer to myWnd. When myWnd is deleted, the destructor will automatically destroy the hWnd by calling the Windows DestroyWindow function. If this is not desired, the hWnd must be detached from myWnd before the myWnd object is destroyed (normally when leaving the scope at which myWnd was defined). The Detach member function does this.
myWnd.Detach();
More About Temporary Objects
Temporary objects are created whenever FromHandle is given a handle that does not already have a wrapper object. These temporary objects are detached from their handle and deleted by the DeleteTempMap functions. The default OnIdle processing in CWinThread automatically calls DeleteTempMap for each class that supports temporary handle maps. This means that you cannot assume a pointer to a temporary object will be valid past the point of exit from the function where the pointer was obtained, as the temporary object will be deleted during the Windows message-loop idle time.
Wrapper Objects and Multiple Threads
Both temporary and permanent objects are maintained on a per-thread basis. That is, one thread cannot access another threads C++ wrapper objects, regardless of whether it is temporary or permanent. As stated above, temporary objects are deleted when the thread which that temporary object belongs enters OnIdle.
To pass these objects from one thread to another, always send them as their native HANDLE type. Passing a C++ wrapper object from one thread to another will often result in unexpected results