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

[Livnat Peer]

On 28/05/12 21:31, Itamar Heim wrote:
> On 05/28/2012 02:35 PM, Ori Liel wrote:
>> Quite a few people liked flow-id, and no one objected to it
>> explicitly, so I'll just go with that.
>>
>> If someone feels strongly against, please reply.
> 
> I still like 'label' better.
> it doesn't have the context of a unique id, and is much more correct to
> what this is - allows the user to label a command (or a set of commands).
> but also doesn't imply it's unique in any way (i.e., it's like a "tag",
> just a better, non overloaded term for it).
> 

I think that flow-id is confusing. This id has nothing to do with flow,
it can aggregate multiple commands and it is not associated with a
specific user flow.

Correlation-Id is a common name for such Id, we took it from the
terminology used in JMS queues, but Microsoft and Oracle are using CID too.

* http://www.microsoft.com/en-us/download/details.aspx?id=23842
*
http://sharepoint.microsoft.com/blogs/GetThePoint/Lists/Posts/Post.aspx?ID=353
*
http://docs.oracle.com/cd/B14099_19/integrate.1012/b25709/com/oracle/bpel/client/CorrelationId.html


>>
>> Ori
>>
>> ----- Original Message -----
>> From: "Michael Pasternak"<mpastern at redhat.com>
>> To: "Moti Asayag"<masayag at redhat.com>
>> Cc: "Ori Liel"<oliel at redhat.com>, engine-devel at ovirt.org
>> Sent: Monday, May 28, 2012 2:26:10 PM
>> Subject: Re: [Engine-devel] REST-API: Exposing correlation-ID
>>
>> On 05/15/2012 05:31 PM, Moti Asayag wrote:
>>> On 05/14/2012 02:19 PM, Ori Liel wrote:
>>>>> No decision about the name of the parameter yet, and this is
>>>>> blocking me.
>>>>>
>>>>> Names that were suggested so far:
>>>>>
>>>>> * flow-id
>>
>> +1
>>
> 
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel