ResolvableIdcan be directly asked for such content, keeping the two together. The equals method for ResolvableId should not consider the content, caching mechanism, etc. All ContentIds should equate when their toByteArray methods return the same byte array and the
CidSchemes are the same (
cids1.equals(cids2)). ResolvableId has a repo because it must have a way to resolve. If it contains an actual reference to the HasContentId, the repo returned may be a simple implementation that only fulfills requests for this one ResolvableId. Another option is to insert the HasContentId into a repo (with the same CidScheme of course) obtained elsewhere and return that.
|Modifier and Type||Method and Description|
Depending on the origin of the ResolvableId this may just be a
HasContentId resolve() throws ContentResolutionException
CaBytesor it may be something more specific, either cached from where this ResolvableId was created or recreated using type information from a serialization.