shuttle: Change internal protocol #485
Labels
blocked
Blocked by another feature, request or issue.
P-Low
Low Priority
refactoring
Major change to features
Currently, shuttle utilizes a low level request-response protocol with the idea of being able to benefit from utilizing the transport for handling security without any redundant security methods that may be done via pubsub for specific request to a specific peer while waiting on a response from shuttle for specific request (eg registering the identity, updating, requesting mailbox, etc)., however because of the way things are designed currently, we have to send commands to the behaviour to send the request to the peer, while awaiting on a response to be sent via oneshot from the behaviour. While generally this would be fine, this, in some way, introduces some complexity between having to split the protocol between a "client" and "server", having to introduce additional channels to warp-ipfs, etc. After evaluating things, this protocol may benefit from being change from the low level behaviour to something more higher.
Thoughts:
Notes:
The text was updated successfully, but these errors were encountered: