8/28/2008 The IDccManSink interface is implemented by a desktop client application that needs to be notified by the Windows Embedded CE connection manager when a device connects or disconnects.
.gif) Note: |
|---|
| The IDccManSink interface is designed for event notifications only and is executed by RAPI internal thread. Therefore, you should not make RAPI function calls other than CeRapiInitEx and CeRapiUninit from within the methods of the interface. A RAPI application should only call other RAPI functions from its own thread. |
Methods in Vtable Order
| IDccManSink methods | Description |
| IDccManSink::OnLogIpAddr | Indicates that an Internet Protocol (IP) address has been established for communication between the desktop computer and the Windows Embedded CE–based device. |
| IDccManSink::OnLogTerminated | Indicates that the Windows Embedded CE connection manager has been shut down. |
| IDccManSink::OnLogActive | Indicates that a connection is established between the client application and the connection manager. |
| IDccManSink::OnLogInactive | Indicates a disconnection, or disconnected state, between the desktop computer and the Windows Embedded CE–based device. |
| IDccManSink::OnLogAnswered | Indicates that the Windows Embedded CE connection manager has detected the communications interface. |
| IDccManSink::OnLogListen | Indicates that a connection is waiting to be established between the desktop computer and the Windows Embedded CE–based device. |
| IDccManSink::OnLogDisconnection | Indicates that the connection manager has terminated the connection between the desktop computer and the Windows Embedded CE–based-device. |
| IDccManSink::OnLogError | Indicates that the connection manager failed to start communications between the desktop computer and the Windows Embedded CE–based device. |
Requirements
| Header | dccole.h |
| Windows Embedded CE | Windows CE 1.0 and later |
| Windows Mobile | Pocket PC 2002 and later, Smartphone 2002 and later |
See Also