Well, it is a good idea and I will try my best to compare two of them. Willem Jiang <willem.ji...@gmail.com> 于2018年11月1日周四 下午5:14写道：
> Hi Zheng > > Thanks for the information. As you know the specification has lots of > information. > Could you break down it into smaller section and we could do some > comparison with current Saga implementation? > For example, the LRA is based on the Restful Service and the > Transaction ID is passed through the HTTP headers. The LRA Client API > is much like our Omega API, but we don't expose much of the detail > from the client side. > > Currently we are thinking about to do some enhancement on the Saga > protocol by helping user to release the lock once the Saga transaction > is finished[1]. I think we may contribute this use case back to the > lra specification by starting the discussion first. > > [1]https://issues.apache.org/jira/browse/SCB-1006 > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > On Thu, Nov 1, 2018 at 3:56 PM Zheng Feng <zh.f...@gmail.com> wrote: > > > > Hi all, > > > > I think we need to have the eyes on this specification. The LRA (Long > > Running Action) [1] tries to introduce some Saga like APIs in the micro > > services. These are similar to our omega and alpha APIs currently. Now > they > > are going to ask the community for some input [2], and I think we can > > contribute some ideas from our side especially with the coordinate > service > > design. > > > > Thanks, > > Zheng Feng > > > > [1] https://github.com/eclipse/microprofile-lra > > [2] https://groups.google.com/forum/#!topic/microprofile/vWM0eXE8gYc >
