Important:
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.
A version of this page is also available for
4/8/2010

These constants define the priority of the connections that are defined in the dwPrioritymember of the CONNMGR_CONNECTIONINFOstructure and requested by the application. Connection Manager arbitrates among multiple connection requests, trying to satisfy as many as possible at a time, but giving preference to higher priorities.

The following table shows the Connection Manager priority constants.

Value Description

CONNMGR_PRIORITY_USERINTERACTIVE

A user-initiated action caused this request and the Connection Manager user interface (UI) is currently pending on the creation of this connection. This is appropriate for an interactive browsing session, or if the user selects "MORE" at the bottom of a truncated mail message.

CONNMGR_PRIORITY_USERBACKGROUND

A user-initiated connection that has recently become idle.

CONNMGR_PRIORITY_USERIDLE

Interactive user task that has been idle for an application-specified time. The application should toggle the state between this constant and CONNMGR_PRIORITY_USERINTERACTIVE as the user uses the application. This helps Connection Manager optimize responsiveness to the interactive application, while sharing the connection with background applications.

CONNMGR_PRIORITY_HIPRIBKGND

High-priority background connection.

Using this priority setting will suppress error messages when the connection cannot be established. Use Connection Manager Control Flag Constantsto suppress error messages.

CONNMGR_PRIORITY_IDLEBKGND

Idle-priority background connection.

CONNMGR_PRIORITY_EXTERNALINTERACTIVE

Connection is requested on behalf of an entity that is external to Connection Manager, but the current session is an interactive task that has been initiated by the user. For example, the AT Command Interpreter does not directly go through Connection Manager, but Connection Manager can detect and, if necessary, disconnect any connections established for this application.

CONNMGR_PRIORITY_LOWBKGND

Lowest priority. Only connects if another higher-priority client is already using the same path. This option is ideal for an application that wants to exchange information packets if a connection is already active but would not initiate the establishment of a connection for this purpose. An example for such a scenario is an Instant Messenger application that wants to send and receive messages only when a connection is already active. Also connects if a cached connection to the same network exists and each connection along the connection path is automatically connected. DTPT, Wi-Fi, wired Ethernet, GPRS and 1xRTT connections are considered automatically connected. CSD connections are not considered automatically connected.

Requirements

Header connmgr.h
Windows Embedded CE Windows CE .NET 4.2 and later, Windows Embedded NavReady 2009

See Also

Reference

CONNMGR_CONNECTIONINFO

Other Resources


500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.