You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eventmesh.apache.org by GitBox <gi...@apache.org> on 2022/01/26 04:12:21 UTC
[GitHub] [incubator-eventmesh] liwenzheng opened a new issue #747: [Feature] connection stateless
liwenzheng opened a new issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues.
### Feature Request
what do you think ?
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021955962
@qqeasonchen
There are only four directions:
1. Client instance
2. Mesh in the cluster
3. Mesh outside the cluster
4. Store in the store.
Just make the router and find the corresponding session or API according to the command
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng commented on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng commented on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021948556
> @liwenzheng will all the command will be changed？
> No, because the state is defined on the client side, the state needs to be maintained on the mesh side. For mesh, it only cares about which client it is, not what the client does. Mesh just needs to find the corresponding client according to the command and push the event. Command does not need to be changed, but some attributes need to be added to the protocol.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng commented on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng commented on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021955962
@qqeasonchen
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021955962
@qqeasonchen
消息能去的地方只有四种：1.client实例 2.集群内mesh 3.集群外mesh 4.存储到store。只需要做好这个路由器，根据 Command 就能找到相应的session或者api
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021955962
@qqeasonchen
There are only four places where events can go:
1. Client instance
2. Mesh in the cluster
3. Mesh outside the cluster
4. Store in the store.
Just make the router and find the corresponding session or API according to the command
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021955962
@qqeasonchen
There are only four directions:
1. Client instance
2. Mesh in the cluster
3. Mesh outside the cluster
4. Store in the store.
Just make the router and find the corresponding session or API according to the command
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021955962
@qqeasonchen
There are only four directions:
1. Client instance
2. Mesh in the cluster
3. Mesh outside the cluster
4. Store in the store.
Just make the router and find the corresponding session or API according to the command
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021948556
> @liwenzheng will all the command will be changed？
> @qqeasonchen No, because the state is defined on the client side, the state needs to be maintained on the mesh side. For mesh, it only cares about which client it is, not what the client does. Mesh just needs to find the corresponding client according to the command and push the event. Command does not need to be changed, but some attributes need to be added to the protocol.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng commented on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng commented on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1023010289
> @liwenzheng Hi, I have some questions.
>
> 1. How to find the event target by command?
> 2. Besides adding additional attributes to command, what else should be refactoring and modified?
> 3. How to pub/sub event for client in this architecture?
First of all, you have to have the architecture of event flow, and then you have the pub / sub mode
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] zmt-Eason commented on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
zmt-Eason commented on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1022976138
@liwenzheng Hi, I have some questions.
1. How to find the event target by command?
2. Besides adding additional attributes to command, what else should be refactoring and modified?
3. How to pub/sub event for client in this architecture?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng commented on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng commented on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1023010839
@zmt-Eason First of all, you have to have the architecture of event flow, and then you have the pub / sub mode
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng commented on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng commented on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021959222
消息能去的地方只有四种：1.client实例 2.集群内mesh 3.集群外mesh 4.存储到store。只需要做好这个路由器，根据 Command 就能找到相应的session或者api
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng removed a comment on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng removed a comment on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021959222
消息能去的地方只有四种：1.client实例 2.集群内mesh 3.集群外mesh 4.存储到store。只需要做好这个路由器，根据 Command 就能找到相应的session或者api
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021955962
@qqeasonchen
There are only four directions:
1. Client instance
2. Mesh in the cluster
3. Mesh outside the cluster
4. Store in the store.
Just make the router and find the corresponding session or API according to the command
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] qqeasonchen commented on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
qqeasonchen commented on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021900204
@liwenzheng will all the command will be changed？
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021955962
@qqeasonchen
There are only four places where event can go: 1 Client instance 2 Mesh 3 in the cluster Mesh 4 outside the cluster Store in store. Just make the router and find the corresponding session or API according to the command
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng removed a comment on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng removed a comment on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1023010289
> @liwenzheng Hi, I have some questions.
>
> 1. How to find the event target by command?
> 2. Besides adding additional attributes to command, what else should be refactoring and modified?
> 3. How to pub/sub event for client in this architecture?
First of all, you have to have the architecture of event flow, and then you have the pub / sub mode
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng commented on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng commented on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1023080422
@zmt-Eason You can add wechat group and let's chat on wechat
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021955962
@qqeasonchen
There are only four directions:
1. Client instance
2. Mesh in the cluster
3. Mesh outside the cluster
4. Store in the store.
Just make the router and find the corresponding session or API according to the command
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org
[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #747: [Feature] connection stateless
Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #747:
URL: https://github.com/apache/incubator-eventmesh/issues/747#issuecomment-1021955962
@qqeasonchen
There are only four places where news can go: 1 Client instance 2 Mesh 3 in the cluster Mesh 4 outside the cluster Store in store. Just make the router and find the corresponding session or API according to the command
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org