Share via

Closing the QOS Connection

  • Article

There are a number of ways to close a QOS-enabled connection. Generally, any event that closes a socket also ends RSVP SP servicing on the socket. Examples of events that cause the RSVP SP to stop providing QOS functionality on a socket include:

Note  RSVP signaling is not supported on Windows XP, Windows Server 2003, or later versions of Windows.

  • Using the closesocket function to close the socket.
  • Using the shutdown function to disable sends or receives on a socket. Note, however, that shutting down only the receive capabilities leaves the QOS-enabled send capabilities for the socket intact, and that shutting down only the send capabilities of a socket leaves the QOS-enabled receive capabilities for the socket intact as well.
  • Using the WSAConnect function with the name parameter set to NULL.
  • Using the WSAIoctl function with the SIO_SET_QOS IOCTL opcode, in which the ServiceType member corresponding to SendingFlowspec or ReceivingFlowspec (both of which are of FLOWSPEC) is set to SERVICETYPE_NOTRAFFIC or SERVICETYPE_BESTEFFORT.
    • Note that setting SERVICETYPE_NOTRAFFIC or SERVICETYPE_BESTEFFORT selectively can disable RSVP SP service for sending and receiving individually. For example, setting the ServiceType member of SendingFlowspec to SERVICETYPE_NOTRAFFIC or SERVICETYPE_BESTEFFORT only terminates QOS servicing for sending, and setting the ServiceType member of ReceivingFlowspec to SERVICETYPE_NOTRAFFIC or SERVICETYPE_BESTEFFORT only terminates QOS servicing for receiving.