Ish1yu commented on issue #4787: URL: https://github.com/apache/eventmesh/issues/4787#issuecomment-2003288218
I'm sorry, I didn't understand some descriptions. Isn't there three existing nettyserver? One implementation of tcp, one implementation of http, and another implementation of grpc, [http server can be transformed to the connector, etc.], this is not understood, [connector is not limited to the process level, can be thread level] I think this design is very reasonable, I think the design is not perfect. [connector currently passes through too many nodes, considering to optimize memory mode storage], the existing connector does not pass tcp to runtime, and then the runtime carries out subsequent processing. My solution is to change the original network communication to method call, that is, memory processing. As for switching to distruptor, don't you need to write an eventmesh-storage-plugin? Or does the connector put in the distruptor and the runtime gets it from the distruptor? I haven't learned [filter\transformer] here, [connector(as a standalone function)], isn't this issue abo ut how to integrate connector into runtime，How come independent again? 不好意思，我有一些描述没有看懂，现有的nettyserver不是有三个吗？一个实现的tcp，一个实现的http，还有一个实现的grpc，【http server可以改造对应connector等等】，这个没有理解，【connector不局限为进程级别，可以是线程级别】我认为这样设计很合理，我想到的设计还不完善，【 connector 现有经过的节点过多，考虑优化内存模式的存储】，现有的connector不是由自身tcp到runtime，再由runtime进行后续处理，我的方案是把原网络通信改为方法调用，也就是内存的处理，至于改用distruptor不是需要写一个eventmesh-storage-plugin吗？还是说要connector放入distruptor，runtime再从distruptor中获取呢？【filter\transformer】这里我还没学习，【connector(作为独立的function)】，这个issue 不是讨论如何把connector集成进runtime吗，怎么又独立了？ -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
