|This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.|
The Message Queuing (MSMQ) service in Windows CE makes it possible for distributed applications to communicate with each other across networks and systems that may be offline temporarily. To accomplish this, applications send messages to a queue, which may be located on the same device as the sending or receiving application or on another device available to both applications. When the receiving application is restarted, or the network connection is reestablished, the receiving application reads the messages stored in the queue. The receiving application can be on another Windows CE–based device or on any device running Windows NT (version 4.0) or Windows 2000. This communication takes place without the need for applications to establish, maintain, or even know about the communication conduit being used. This means that with the MSMQ application programming interface (API) you can create distributed applications without the programming overhead associated with creating and maintaining network connections and persistent data buffering.
Support for a subset of the Win32 MSMQ API was added to Windows CE in version 2.12 and additional functionality was provided in version 3.0. The standard MAXALL and MINCOMM configurations both support message queuing. A custom Windows CE platform supports message queuing if it includes the MSMQRT module.
The MSMQ add-on pack, version 1.0.132, extends MSMQ support equivalent to that provided in version 3.0 to the following devices and platforms:
Software developers who want to add MSMQ functionality to existing devices can download this add-on package from http://msdn.microsoft.com/downloads.