使用 ACE 这个庞大的自适应通信环境并不是最佳的工程选择。这个例子以及其中的文档演示了如何使ACE与MFC和谐共处，解决因调用不当导致内存泄露、宽窄字符集接口等问题。

实现的例子使用ACE的Reactor 和 Task 实现了接收者-伴随处理模型，用消息队列实现了大数据包拼接，但要注意一个例程自发自收会发生阻塞, 这与使用API大不相同。ACE 太大了，很恼火。ACE 的 ACE_warppers.sln 使用VC2010进行了改变，添加了UnicodeDebug, UnicdoeRelease两个模式，对应多字节、Unicdoe的四种库命名为 ACE.dll, ACEd.dll, ACEu.dll, ACEud.d-Use of ACE Adaptive Communication Environment in this huge project is not the best choice. This example and the documentation which shows how ACE and MFC harmony to solve memory leak due to improper call, the interface width character set issues. Examples of implementation of the Reactor and the use of ACE Task implementation of the receiver- with processing model, with the message queue data packets to achieve a large mosaic, but note that since the resumption of a routine voluntary blocking occurs, which is very different from using the API. ACE is too large, very angry. ACE' s ACE_warppers.sln use VC2010 for a change, add UnicodeDebug, UnicdoeRelease two modes, corresponding to multi-byte, Unicdoe four library named ACE.dll, ACEd.dll, ACEu.dll, ACEud.dll