Skip to content
This repository has been archived by the owner on Nov 15, 2020. It is now read-only.

The role of network events #266

Open
iasoon opened this issue Sep 22, 2018 · 0 comments
Open

The role of network events #266

iasoon opened this issue Sep 22, 2018 · 0 comments

Comments

@iasoon
Copy link
Member

iasoon commented Sep 22, 2018

Right now, network communication is implemented as request/response style RPC calls. We take a MOZAIC-connection and attach request handler to it, which has a type of SomeEventType -> Result. When the remote party then sends a request, we just connect it to the assigned handler. Apart from requests, connection events (Connected, Disconnected, Quit) can also happen, Right now this is just bolted on to the handler system, where the produced result is ignored. This might not really be ideal. What would be a better way to solve this?

The nice part about doing it this way is that there is one from the network, containing both events sent by the remote party and produced by the connection status.

All input welcome!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant