Pavel Simerda wrote:
On Thu, 14 Aug 2008 10:38:42 -0600 Peter Saint-Andre <[EMAIL PROTECTED]> wrote:Pavel Simerda wrote:
<snip/>
Since developers of Jabbim would like to use BoB for emoticons exchange (possibly in a way similar to the one used by Pidgin developers, might be neat to spec it out sometime), I'd like to ask whether it would be possible to reconsider using hashes instead the UUID for identification.We use hashes in XEP-0084 (User Avatar): http://www.xmpp.org/extensions/xep-0084.html So it might make sense to use them here as well.Yep, they would be good to incorporate in ConentID. Btw, the hash would be enough itself (without CID) but we want to use CID URIs.
I agree that hashes would be enough (as in XEP-0084), but here we want to use CIDs for cross-referencing.
Where are those specified? I see a bit of information about that in RFC4122 but not a lot of details.You can use hash-based UUIDs.They are only hash-based and they are (hopefully) unique to a particular sequence of bytes. They don't serve the same purpose as e.g. sha1 mostly because the full sha1 hash doesn't fit in UUID.
I'll have to see where those are specified. <snip/>
2) Add one additional form of CID: "hash-value"@"hash-function".xep0231.xmpp.org.(the concrete syntax serves as an example, not final syntax) The hash functions would be "sha1", "sha256" and possibly other ones too and the computed hash value would be based on both *content type* and *content data* (needs more precise spec.). This would also be an exception from forced "per JID" caching.Or if people define emoticon bundles then the images could be identified by the domain of the entity that hosts the bundle, perhaps an open-source project or whatever. /psaThis would break the hash function use case. We want same data (including type) to have same ContentID uri for global sharing (most probably with a constant domain part).
I don't see any big difference between: cid:[email protected] and: cid:[email protected] or: cid:[email protected] or whatever. Why do we need centralization of the address space? /psa
smime.p7s
Description: S/MIME Cryptographic Signature
