-
Notifications
You must be signed in to change notification settings - Fork 9
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.
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
[DID Reference] REQUIREMENT: Ability to ping
a DID Resolver to see if it is alive and responsive
#27
Comments
Thanks @mwherman2000 this seems like a useful feature. I'm not sure if this should be part of the DID Resolution spec, since it's not directly related to the resolution process itself. Instead it could be an implementation-specific feature. But let's discuss. |
@peacekeeper I think we need to revisit and rework the Purpose of the DID Resolution spec this week - especially wrt scope. I'm perhaps thinking more broadly as the DID Resolution spec being the "API" for a DID Resolver ...which embraces then extends actual DID resolution. QUESTION: If functions/capabilities like |
it would be much better if a real json object were returned - same with error - in fact any invalid request should be a fine ping. |
Closed in favor of #32 Use case 5 |
Ability to
ping
a DID Resolver to see if it is alive and responsive.Sample request:
did:?ping
Response: A DID Resolver Response containing a JSON subelement containing a current TOD timestamp in milliseconds.
The text was updated successfully, but these errors were encountered: