Hi Haishi,

Please feel free to send a PR to keep the FAQ updated.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Sep 7, 2018 at 2:25 PM yhs0092 <[email protected]> wrote:
>
> Hi, maybe some questions in our website
> https://docs.servicecomb.io/java-chassis/en_US/question-and-answer/question_answer.html
> should be updated.
>
>
> For example, there is a question
>
> Q: 框架中引入了vertx会有什么好处?
>
> A: 
> 启用vertx的标准工作模式更强大,不过对业务人员要求就有些高了,目前还没开放业务接口出来。vertx标准的reactive工作模式,要求业务代码中不能有任何的block
>  wait,sleep,大循环,总之不能有阻塞,做到这一点,就可以用更少的CPU,提供更多的服务。
>
> I guess this answer is talking about reactive mode, and we have provided this 
> feature.
>
> And there is an answer says that JavaChassis does not support generic param,
>
> Q: ServiceComb不支持泛型
>
> A: 明确不支持,需要修改接口,接口修改后需要修改版本号,以免consumer还是使用旧的版本。
>
> but we have supported generic param and response type. See 
> https://docs.servicecomb.io/java-chassis/en_US/build-provider/interface-constraints.html
>
>
> Yours sincerely
>
>
> Yao Haishi
> [email protected]
>
>
> On 9/5/2018 17:24,Zen Lin<[email protected]> wrote:
> To my opinion, if we have faqs,  we should make sure there is a search
> entry that can search questions directly by keyword.
> Usually, opensource projects use google search embeded into the website,
> but I am not sure if  the google search can search out them.
>
> If we can not reach that, I suggest we just list them within the user
> guide, thus when users use user guide, they can also get the corresponding
> faqs.
>
>
> Best Regards,
> ---
> Zen Lin
> [email protected]
> Focused on Micro Service and Apache ServiceComb
>
>
> DeanLee <[email protected]> 于2018年9月5日周三 下午4:21写道:
>
> Hi all,
> I want to translate Q & A of the website for English as blew, but
> here is a problem.
> http://servicecomb.incubator.apache.org/cn/faqs/
> For now, we have two pages of Q&A(another one in UserGuide).
> Should we merge it together or keep it split as before
>
> https://docs.servicecomb.io/java-chassis/en_US/question-and-answer/question_answer.html
>
>
> Best Regards,
> Dean

Reply via email to