Media Query Engine Architecture (Windows CE 5.0)

Send Feedback

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

The MQE manages the connection between your application and any number of UPnP Media Servers on the local network.

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 DirectShow. The application communicates with the MQE through a public API that is documented here: Media Query Engine Reference. It does this when it needs information from, or about the media servers.

This information can be:

• A listing of the available media servers on the network. This allows the application to display this list to a user, who chooses which server to connect to.
• A listing of media stored on the server that the application can allow a user to browse.
• Specifics about a particular piece of media, which the application can pass to DirectShow, which will 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 Server. It communicates with the server through UPnP server proxies provided by the Media Query Engine.

In This Section

• Error Handling
  Describes possible errors and their resolution.
• Discovery and Description
  Describes how the Media Query Engine manages the UPnP processes of discovery and Description.
• Authorization and Registration
  Describes how the Media Query Engine manages the processes of authorization and registration.

Related Sections

Media Query Engine

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.