[Engine-devel] REST-API: Exposing correlation-ID

Itamar Heim iheim at redhat.com
Tue May 15 21:18:35 UTC 2012


On 05/15/2012 05:44 PM, Miki Kenneth wrote:
>
>
> ----- Original Message -----
>> From: "Itamar Heim"<iheim at redhat.com>
>> To: "Eoghan Glynn"<eglynn at redhat.com>
>> Cc: engine-devel at ovirt.org
>> Sent: Monday, May 14, 2012 7:07:07 PM
>> Subject: Re: [Engine-devel] REST-API: Exposing correlation-ID
>>
>> On 05/14/2012 07:05 PM, Eoghan Glynn wrote:
>>>
>>>
>>>>>> * MetaTask-ID
>>>>
>>>> -1, too pompous?
>>>
>>> Me, pompous? Never! ;)
>>>
>>>> a maybe to remove the "ID" from name, since there is no uniqueness
>>>> guarantee.
>>>
>>> Sure, MetaTask-Tag for example would be less connoting of
>>> uniqueness.
>>
>> I like 'Tag'
>> only problem is we have tags in the system already...
>>
>> looking for something in same area - how about just calling this
>> field
>> 'label'
> Agreed. I like Tag cause it's short... need to find something similar.
> cmd-id?

cmd represents a single command in backend.
id represent something unique.

I'm liking 'label' more and more, since it doesn't imply uniqueness.

>>
>>>
>>> But in general, I'd +1 any of the options that aren't suggestive of
>>> this being a purely log-oriented thing.
>>>
>>> Cheers,
>>> Eoghan
>>
>> _______________________________________________
>> Engine-devel mailing list
>> Engine-devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>




More information about the Engine-devel mailing list