It comes up a lot, so apparently it happens.

  There are a few dimensions to interop:

  * Hash algorithms
  * Node location algorithms
  * Flag usage
  * Content encoding

There is at least one common hash algorithm I think every client supports.

There are two node location algorithms many clients support -- at least one they all do (should?)

Someone put together a matrix of flag usage recently. It seems there are commonalities, but mostly by coincidence. This needs work.

Content encoding varies greatly. Strings are somewhat easy, though not universal, but there are other common types that could handle a common encoding.

--
Dustin Sallings (mobile)

On Jan 29, 2008, at 12:58, Ciaran <[EMAIL PROTECTED]> wrote:


       There is some flag space reserved for something like flags that
aren't supposed to be exposed in the client APIs, but I'm having
trouble seeing the point.  I'm under the impression that not a lot of
users make heavy use of the flags for anything other than content
encoding.  That is, at least, where all the confusion is.

Thats a shame, perhaps I'm an edge case, do most people not share across platforms, or if they do just store 'raw' data ?
- Ciaran

Reply via email to