I think we need to focus on how to use ServiceComb instead of write
another application which only has few audience.
My suggestion is we just break down the requirements and show user
how to do authentication with ServiceComb java-chassis, how to server
the front-end pages with ServiceComb
It sounds a good idea : )
Can you briefly show us the design how to use ServiceComb to build
an e-commerce? thks
Best Wishes & Regards
---
Mabin
郑志鹏 于2019年7月22日周一 上午10:26写道：
> Thanks for you suggestions. I will make sure the is licensed under Apache
> License
Thanks for you suggestions. I will make sure the is licensed under Apache
License and the libraries it uses is compatible. And I will make the
document as detailed as possible.
Liubao (A) 于2019年7月20日周六 下午10:55写道：
> Any samples to use ServiceComb is preferred. I have some questions before
> you
I rethink the idea I proposed, yes, provide low level apis is a bad idea,
and I also don't suggest that let user code use omega-xxx-transport api.
I think the essential issues are three:
1. How to pass tx context info across threads
2. How to asynchronously tell Alpha that Saga is ended or
