Media Query Engine Architecture (Windows Embedded CE 6.0)

1/5/2010

The MQE manages the connection between your application and any number of Universal Plug and Play (UPnP) media servers on the local network.

The following illustration shows the structure of the Media Query Engine (MQE).

In the illustration, the application represents your program, which manages the display of the user interface and playback of audio, still images, and video through Microsoft DirectShow. The application communicates with the MQE through a public API when it needs information from or about the media servers. For more information about the media query engine API, see Media Query Engine Reference.

This information can be:

• A list of the available media servers on the network. This information allows the application to display this list to a user, who chooses which server to connect to.
• A list of media that is stored on the server and that the application can allow a user to browse.
• Details about a particular piece of media, which the application can pass to DirectShow. This information allows DirectShow to stream the media directly from the server. The MQE is not involved in the streaming of media.
• Events that the MQE uses to notify the application about changes in network status, media server status, and media content updates.

The MQE uses UPnP to find and communicate with the media servers. The application communicates with the servers through UPnP server proxies that the MQE provides.

In This Section

• Error Handling
  Describes possible errors and their resolutions.

• Discovery and Description
  Describes how the MQE manages the UPnP processes of discovery and description.

• Authorization and Registration
  Describes how the MQE manages the processes of authorization and registration.

See Also

Concepts

Media Query Engine