[Telepathy] Handle Uniqueness

[Robert McQueen]

Looks good, thanks. Sorry about the delay merging.

Regards,
Rob

Daniel d'Andrada Tenório de Carvalho wrote:
> Alright then. I think the attached patch will do the job.
> 
> Regards,
> Daniel d'Andrada T. de Carvalho - INdT
> 
> ext Robert McQueen wrote:
>> [...] A patch for the spec to clarify this would be
>> cool.
>>
>> Regards,
>> Rob
>>
>> Daniel d'Andrada Tenório de Carvalho wrote:
>>  
>>> Hi,
>>>
>>> The spec (.13) currently doesn't make any statement about its handle
>>> uniqueness. [...]
>>> Anyway, regardless of what option is finally chosen, the uniqueness
>>> concept adopted must be clearly stated in the spec.
>>>
>>> Regards,
>>> Daniel d'Andrada T. de Carvalho - IN
>>>     
> 
> ------------------------------------------------------------------------
> 
> diff -rN -u old-telepathy-spec/telepathy/server/conn.py new-telepathy-spec/telepathy/server/conn.py
> --- old-telepathy-spec/telepathy/server/conn.py	2006-07-21 17:18:10.000000000 +0000
> +++ new-telepathy-spec/telepathy/server/conn.py	2006-07-21 17:18:10.000000000 +0000
> @@ -46,14 +46,16 @@
>      immutable handles, which are unsigned non-zero integers which are valid
>      only for the lifetime of the connection object, and are used throughout the
>      protocol where these entities are represented, allowing simple testing of
> -    equality within clients. Connection manager implementations should
> -    reference count these handles to determine if they are in use either by any
> -    active clients or any open channels, and may deallocate them when this
> -    ceases to be true. Clients may request handles of a given type and name
> -    with the RequestHandles method, inspect the entity name of handles
> -    with the InspectHandles method, keep handles from being released with
> -    HoldHandles, and notify that they are no longer storing handles with
> -    ReleaseHandles.
> +    equality within clients. Handles have per-type uniqueness, meaning that
> +    every (handle type, handle number) tuple is guaranteed to be unique within
> +    a connection and that a handle alone (without its type) is meaningless or
> +    ambiguous. Connection manager implementations should reference count these
> +    handles to determine if they are in use either by any active clients or any
> +    open channels, and may deallocate them when this ceases to be true. Clients
> +    may request handles of a given type and name with the RequestHandles
> +    method, inspect the entity name of handles with the InspectHandles method,
> +    keep handles from being released with HoldHandles, and notify that they are
> +    no longer storing handles with ReleaseHandles.
>      """
>      def __init__(self, proto, account):
>          """
> 


-- 
Robert McQueen
Director, Collabora Ltd.