| Previous | Next |
| STATUS_RECEIVE_PARTIAL | STATUS_RECEIVE_PARTIAL_EXPEDITED |
STATUS_RECEIVE_EXPEDITED
The transport delivered data marked as expedited
Legacy TDI distinguished normal receive indications from expedited data supplied by a remote peer. A client could register a dedicated expedited receive handler; if it did not, the normal receive path could be asked to process the indication with flags describing its special status.
Expedited data is transport-specific and must not be confused with ordinary application priority. The client should preserve the receive flags and protocol context before deciding whether the bytes belong to an urgent control path, an out-of-band mechanism, or a compatibility feature. Migrating old TDI code requires mapping that behavior deliberately rather than silently merging all receives.
What to inspect
- Capture the receive flags and whether a dedicated expedited handler was registered.
- Verify how the underlying transport represents urgent or out-of-band data.
- Keep expedited control data separate from normal application framing when the protocol requires it.
References
- Microsoft: TDI_SET_EVENT_HANDLER
- Microsoft: ClientEventReceive
- Microsoft: TDI_SET_INFORMATION and TDI deprecation
Looking for a different code? Search another status or error code.