Cantor, Scott cantor.2 at
Fri Feb 23 13:18:11 EST 2018

 > Is there simply another type I should be using? Otherwise I see no
> alternative to scripting the whole thing from scratch, by hashing the
> 3-tuple myself.

I'm still not getting it, I think. Are you asking how to get different values out? Or how to deal with the fact that you don't want different values?

Even if you left all the existing properties in place and reused the same salt, you *could* just alter the encoding to BASE32 in the resolver version. And the properties could all be different/duplicated with different names if you wanted a different salt, or you could put the salt inline.

Are you just overlooking the encoding attribute in the ComputedId connector?

Down at the bottom of the table, added in 3.3.2 because we felt it was warranted.

Sorry if I'm still not following the question you're asking.

-- Scott

More information about the users mailing list