You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to suggest that DIDKey could be made into a synchronous DID resolver, since that particular resolver doesn't have any need for async.
This could either simply factoring the body of the DIDKey::resolve method out into a impl DIDKey pub fn resolve_sync, or more formally by making a DIDResolverSynchronous trait, have DIDKey implement that, and add (into ssi/src/did_resolve.rs) an automatically derived impl of DIDResolver for anything impl'ing DIDResolverSynchronous.
Thoughts?
The text was updated successfully, but these errors were encountered:
Random person looking for a simple and correct did:key implementation here: Having an async trait for something purely in-memory and synchronous is overcomplicating it. Would be cool if did-method-key had an inherent impl for resolution and made the resolver trait feature gated, for those of us only interested in that particular method.
I'd like to suggest that DIDKey could be made into a synchronous DID resolver, since that particular resolver doesn't have any need for async.
This could either simply factoring the body of the DIDKey::resolve method out into a impl DIDKey pub fn resolve_sync, or more formally by making a DIDResolverSynchronous trait, have DIDKey implement that, and add (into ssi/src/did_resolve.rs) an automatically derived impl of DIDResolver for anything impl'ing DIDResolverSynchronous.
Thoughts?
The text was updated successfully, but these errors were encountered: