AppSequence Validation Rules
AppSequence information contained in WS-Discovery announcement and response messages (Hello, ProbeMatches, and ResolveMatches). This information is processed and validated by WSDAPI before these messages are passed on to components above the stack (such as Network Explorer or an application calling into WSDAPI).
The following XML shows a sample AppSequence element. The wsd prefix refers to the namespace https://schemas.xmlsoap.org/ws/2005/04/discovery
.
<wsd:AppSequence InstanceId="2"
SequenceId="urn:uuid:369a7d7b-5f87-48a4-aa9a-189edf2a8772"
MessageNumber="21">
</wsd:AppSequence>
WSDAPI ignores stale messages. For each device (uniquely identified by the Endpoint Address in the SOAP Body), WSDAPI ignores any messages with an AppSequence MessageNumber lower than the last message seen.
WSDAPI ignores stale XAddr announcements. If the AppSequence InstanceId is lower than the last InstanceId seen, WSDAPI ignores the XAddrs advertised in the SOAP body. Also, if the InstanceId is the same as previous but the MetadataVersion is lower than the last MetadataVersion, WSDAPI ignores the XAddrs.
WSDAPI ignores duplicate WS-Discovery messages. If two identical WS-Discovery messages are sent to WSDAPI, only the first received will be processed. This is typically only relevant for applications that call directly into the IWSDiscoveryPublisher or IWSDiscoveryProvider interfaces.
Related topics
피드백
https://aka.ms/ContentUserFeedback
출시 예정: 2024년 내내 콘텐츠에 대한 피드백 메커니즘으로 GitHub 문제를 단계적으로 폐지하고 이를 새로운 피드백 시스템으로 바꿀 예정입니다. 자세한 내용은 다음을 참조하세요.다음에 대한 사용자 의견 제출 및 보기