about secio about tentacle HOT 6 CLOSED

You are right, the reason for this way was that it was fast to impl, secio can really only provide the implementation of AsyncRead/AsyncWrite, which is also the method I tried in the go implementation:

https://github.com/driftluo/tentacle-go/tree/master/secio

It would be more concise if the first implementation is this way, and the second is to reduce the overhead of the channel, which is a good thing, but I am currently busy solving other problems I found.

If you are interested, welcome to provide PR implementation, but it should be noted that there can be no break in the protocol

from tentacle.

Ok, I'll try to cleanup the code then make a pull request. On the other hand, the bug I mentioned has to be fixed, therefore, it can not be fully compatible with the original implemention. I guess it is ok since we are not going to use secio directly as a message based protocol.

BTW, would you like to take a bit more on wechat sometime? I do have some questions about rust async coding. Hopefully you can help anyhow.

from tentacle.

BTW, would you like to take a bit more on wechat sometime? I do have some questions about rust async coding. Hopefully you can help anyhow.

you can find me on wechat，but how can I give you the wechat id？

from tentacle.

I can send you mine via your email [email protected], is that ok?

from tentacle.

I can send you mine via your email [email protected], is that ok?

ok

from tentacle.

close by driftluo#23

from tentacle.