docs: event queue connection class design

[r4mmer]

• rendered - phase 1
  • Create an event queue connection class
• rendered - phase 2
  • Organize connection implementation on the wallet-lib
• rendered - phase 2
  • Processing transactions individually

[andreabadesso]

I think it would be great to be more explicit on how the specific events from the reliable integrations feed are going to be handled, like NEW_VERTEX_ACCEPTED and VERTEX_METADATA_CHANGED

[andreabadesso]

The fullnode already sends it decoded, the documentation might not have been updated because this was a change I requested, here is an example input:

{
  "tx_id": "00000000000000a7880484eb5f059e7857973d7c4d131a9bd59389afe6b0dfc6",
  "index": 0,
  "spent_output": {
    "value": 800,
    "token_data": 0,
    "script": "dqkUtlo02wdlNsUJx3OADdSG/uaHGnWIrA==",
    "decoded": {
      "type": "P2PKH",
      "address": "HP9KRutTVPPf5h8jZ3BMwfhkJoZpD1c7if",
      "timelock": null
    }
  }
}

[r4mmer]

Nice catch.

[andreabadesso]

Semi-unrelated to line number, but remember to add a ping/pong mechanism

[r4mmer]

The document of the event queue and the implementation did not have ping/pong anywhere but from what I understand it comes with the websocket lib we use, so I'll add the ping/pong to the design

[andreabadesso]

Autobahn answers the PING frame with a PONG and also disconnects when no messages are received in a window. It also doesn't send a PING, so the implementation must be done in the client

[andreabadesso]

We also need to assert that the stream_id is the same from the last sync

[r4mmer]

Nice catch.

[andreabadesso]

Suggested change

	If the `voided_by` field is the same we can iterate on the outputs and calculate
	If the `voided_by` field is empty we can iterate on the outputs and calculate

[r4mmer]

Used null instead of empty but to the same effect.