Transport Interfaces (Windows Embedded CE 6.0)
1/5/2010
A kernel transport service has two parts: a low-level KITL transport library, and a COM wrapper for the transport library. All KITL clients, including Platform Builder, use the Core Connectivity service host and the COM wrapper to access individual KITL transports.
As with other kernel services, kernel transport services must be hosted by the Core Connectivity Service Host. The service host communicates with the KITL framework layer via COM modules. Every COM layer of the KITL transport implements the following Core Connectivity interfaces:
| Interface | Description |
|---|---|
Provides common methods for connectivity. |
|
Establishes transport streams with a target device. |
|
Supports debug break and target reset from the desktop. |
|
Enables customizing service configurations. |
The transport interfaces, ICcTransport and ICcTransportStream, establish custom transport streams with a target device. Transport interface methods call corresponding KITL interface methods to accomplish a particular task.
The following table provides examples of the relationship between transport interface methods and KITL interface methods.
| Transport interface method | KITL interface method | Action |
|---|---|---|
Creates a named transport stream. |
||
Sends data to a connected target device. |
||
Receives data from a connected target device. |
ICcTransportStream::IsDataAvailable determines if there is data present in the shared memory segment for the stream.
The Core Connectivity KITL interface methods, ICcKitl::Reset and ICcKitl::DebugBreak, provide support for doing a soft reset of the target device from Platform Builder and doing a target break from desktop.