Export (0) Print
Expand All

3.2.1 Abstract Data Model

This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this document.

A TDS client SHOULD maintain the following states:

  • Sent Initial PRELOGIN Packet State

  • Sent TLS/SSL Negotiation Packet State

  • Sent LOGIN7 Record with Complete Authentication Token State

  • Sent LOGIN7 Record with SPNEGO Packet State

  • Logged In State

  • Sent Client Request State

  • Sent Attention State

  • Routing Completed State

  • Final State

 
Show:
© 2014 Microsoft