You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 9, 2022. It is now read-only.
I know Listen returns a listener, and when a relay peer sends STOP to my peer, listener.Accept() gets a conn. So, when will the conn open a stream or accept a stream? Why construct such a conn?
The text was updated successfully, but these errors were encountered:
Listening "/p2p-circuit" makes RelayListener.Accept() called. If a relay hop opens a stream for circuit relay to peer B, then sends STOP, B will call handleStopStream, and write a conn to chan incoming. RelayListener.Accept() will read this conn from chan incoming, send a SUCCESS back, and return the conn.
So, why doesn't handleStopStream send SUCCESS directly? What's the conn used for? It seems this issue #28 is about it, but I can't understand it.
I know
Listen
returns a listener, and when a relay peer sends STOP to my peer,listener.Accept()
gets a conn. So, when will the conn open a stream or accept a stream? Why construct such a conn?The text was updated successfully, but these errors were encountered: