Pavel Simerda wrote:
On Thu, 14 Aug 2008 10:38:42 -0600 Peter Saint-Andre <[EMAIL PROTECTED]> wrote:Pavel Simerda wrote:What I suggest to satisfy the Jabbim developers (and possibly others with similar needs) the following two modifications: 1) Only force UUID if we use the domain part of the JID and forbid re-using these names.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 think it breaks the hash function case. Let's say that the Jabbim team makes a fun new set of emoticons. It hosts those at smilies.jabbim.cz so the CIDs are "[EMAIL PROTECTED]". Then the Pandion team says "hey that's cool, we're going to make our own set of emoticons" so they host those at emoticons.pandora.be and the CIDs for their images are "[EMAIL PROTECTED]". All of these bundles can be freely downloaded and shared, but they "belong" to the people who created them in the first place (Jabbim, Pandora, Psi, Kopete, Adium, third-party graphic artists, whatever).
Peter
smime.p7s
Description: S/MIME Cryptographic Signature
