Client-server stack for Web3! Turn your Raspberry Pi to a BAS server in minutes and enjoy the freedom of decentralized Web with a superior user experience!
The current implementation for subscription over graph protocol does not support closing the connection.
I can think of different reasons which may cause a connection to close:
The subscriber on the client-side decides to close the connection
The subscriber on the client-side loses connection
The BOX app decides to close an open connection due to a timeout
In almost every scenario, the BOX app needs to know some identification about the client (maybe peerID).
On the other hand, at the protocol level, there should be the ability to send an unsubscribe command. (currently, the protocol schema does not cover different types of command)
The current implementation for subscription over graph protocol does not support closing the connection.
I can think of different reasons which may cause a connection to close:
In almost every scenario, the BOX app needs to know some identification about the client (maybe
peerID).On the other hand, at the protocol level, there should be the ability to send an
unsubscribecommand. (currently, the protocol schema does not cover different types of command)