New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Strict ws-discovery support #5

Open

1 of 4 tasks

roncapat opened this issue Apr 14, 2019 · 0 comments

Owner

roncapat commented Apr 14, 2019 •

edited

Loading

fallback to epRefAddr to obtain a network-resolvable URI if no XAddrs present

if the value of this element is not a network-resolvable transport address, such transport address(es) are conveyed in a separate d:XAddrs element

support discovery proxies

Clients listen for this signal that one or more DP are available, and for subsequent searches, Clients do not send Probe and Resolve messages multicast but instead unicast directly to one or more DP whilst ignoring multicast Hello and Bye from Target Services.

Check application instance ID and sequence ID (and discard older messages??)
Update information in database only if MetadataVersion has changed

roncapat changed the title ~~String ws-discovery support~~ Strict ws-discovery support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment