You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eventmesh.apache.org by 林** <je...@163.com> on 2022/05/16 11:47:41 UTC

Biweekly Meeting of EventMesh Developers on May 12th, 2022

Biweekly Meeting of EventMesh Developers on May 12th, 2022


Introduction to the content of this regular meeting

Video recording:

https://meeting.tencent.com/user-center/shared-record-info?id=101ae371-2d58-4c34-b6f7-4cc1b6e07506&from=3

documents:

https://docs.qq.com/doc/DQkdlV0ZhdWZGRXFB?u=fcd8162f05b9453190f79945ab2d66ea&&_t=1652408301536

topic & summary:

1、Dashboard feature        ——xiaoyang liu

The first-stage tasks have been listed, and the function points have been split.

2、WebHook feature        ——laohu

The detailed design scheme is discussed. As a result, it is necessary to support the default configuration storage and not rely on nacos.

3、Route&Fliter feature    ——mikexue

Conduct scheme research and discussion.

4、Transformation of Http request for EventMesh    ——mikexue、laohu

Compatible with requests from em sdk and external http requests such as webhook, and discuss the unified transformation scheme.




Apache Eventmesh

2022.05.16





 

Re: Biweekly Meeting of EventMesh Developers on May 12th, 2022

Posted by Eason Chen <ch...@apache.org>.
Thanks Jeff, nice work~

On Mon, May 16, 2022 at 7:47 PM 林** <je...@163.com> wrote:
>
> Biweekly Meeting of EventMesh Developers on May 12th, 2022
>
>
> Introduction to the content of this regular meeting
>
> Video recording:
>
> https://meeting.tencent.com/user-center/shared-record-info?id=101ae371-2d58-4c34-b6f7-4cc1b6e07506&from=3
>
> documents:
>
> https://docs.qq.com/doc/DQkdlV0ZhdWZGRXFB?u=fcd8162f05b9453190f79945ab2d66ea&&_t=1652408301536
>
> topic & summary:
>
> 1、Dashboard feature        ——xiaoyang liu
>
> The first-stage tasks have been listed, and the function points have been split.
>
> 2、WebHook feature        ——laohu
>
> The detailed design scheme is discussed. As a result, it is necessary to support the default configuration storage and not rely on nacos.
>
> 3、Route&Fliter feature    ——mikexue
>
> Conduct scheme research and discussion.
>
> 4、Transformation of Http request for EventMesh    ——mikexue、laohu
>
> Compatible with requests from em sdk and external http requests such as webhook, and discuss the unified transformation scheme.
>
>
> Apache Eventmesh
>
> 2022.05.16
>
>
>
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: users-help@eventmesh.apache.org


Re: Biweekly Meeting of EventMesh Developers on May 12th, 2022

Posted by Eason Chen <ch...@apache.org>.
Thanks Jeff, nice work~

On Mon, May 16, 2022 at 7:47 PM 林** <je...@163.com> wrote:
>
> Biweekly Meeting of EventMesh Developers on May 12th, 2022
>
>
> Introduction to the content of this regular meeting
>
> Video recording:
>
> https://meeting.tencent.com/user-center/shared-record-info?id=101ae371-2d58-4c34-b6f7-4cc1b6e07506&from=3
>
> documents:
>
> https://docs.qq.com/doc/DQkdlV0ZhdWZGRXFB?u=fcd8162f05b9453190f79945ab2d66ea&&_t=1652408301536
>
> topic & summary:
>
> 1、Dashboard feature        ——xiaoyang liu
>
> The first-stage tasks have been listed, and the function points have been split.
>
> 2、WebHook feature        ——laohu
>
> The detailed design scheme is discussed. As a result, it is necessary to support the default configuration storage and not rely on nacos.
>
> 3、Route&Fliter feature    ——mikexue
>
> Conduct scheme research and discussion.
>
> 4、Transformation of Http request for EventMesh    ——mikexue、laohu
>
> Compatible with requests from em sdk and external http requests such as webhook, and discuss the unified transformation scheme.
>
>
> Apache Eventmesh
>
> 2022.05.16
>
>
>
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org