[Devel] uri-map: what is the `map` parameter for?

[Gabriel Beddingfield]

On 07/18/2011 05:21 PM, David Robillard wrote:
>> Deprecating the `map` parameter should be sufficient... even if you
>> have to say "but for use with the events extension, you must pass the
>> events extension URI as the `map` parameter" or some such thing.
>
> That is exactly what the event extension says, and is exactly the
> problem.

OK, I see it now.  It's in the intro to the header.  I was looking just 
at the doc for LV2_Event::type.

> Put simply:
>
> We need, in general, a method to map/unmap a URI to/from an integer.  We
> do *not* have this.  We have a method to map a URI to/from a *pair* of
> integers, i.e. we have several URI-integer namespaces.
>
> The consequence of this is a big ugly mess of having to keep track of,
> and convert between, contexts, and makes the whole thing much more
> confusing than it should be.

Agreed.  Thanks for clarifying what the mess is, too.  (Really).

> While we're on the topic, using string interning instead is also an
> option if we're going to change how we deal with URIs quickly.  That
> makes unmapping trivial... but pointers are not a fixed size across
> machines.

True.

My preference is a system like X11 Atoms.

-gabriel