It looks like you try to mix the success scenario, failure and compensate scenario, timeout scenario in the one picture ? I think it could be better to separate into the different scenarios. As Willem mentioned, the timeout scenario is much more complicated. Anyway, this is a good idea to find out how we handle the saga events.
Btw, I think this could be very helpful for us to define the state machine of the alpha server. Thanks for your contributions ! Regards, Zheng Feng zhang_...@boco.com.cn <zhang_...@boco.com.cn> 于2019年3月21日周四 下午3:25写道： > This is a light version > > > https://raw.githubusercontent.com/coolbeevip/servicecomb-pack-notes/master/ServiceComb%20Alpha%20Saga/assets/sequence-booking-request-hotel-timeout.png > > 张 磊 > ------------------------------------------------ > 部门: 亿阳信通IT运维支撑产品线 > 地址: 北京市海淀区杏石口路99号西山赢府商务中心2410 > 邮编: 100093 > 手机: 18610099300 > 移邮：zhang_...@boco.com.cn > > > 在 2019年3月21日，上午11:47，zhang_...@boco.com.cn 写道： > > > > The following link is a sequence diagram, step 4 cannot be compensated. > Will this happen? > > > > > https://github.com/coolbeevip/servicecomb-pack-notes/blob/master/ServiceComb%20Alpha%20EventScanner/assets/sequence-booking-request-hotel-timeout.png?raw=true > > > > coolbeevip > > ———————————————————————— > > BOCO > > > > > > > >
