Spike/ws

[jackkav]

under exploration

• open connection handling
• contrasting push updates(event emitter chains) / pull updates(polling data model)
• request model
• high traffic cases
• contrasting solving state problems in renderer / solving state problems in main

decisions:

• instance dictionary is one-to-one [requestId]: [WebSocket]
• use same request model as http, signified with a custom method set to WS,
• note custom method feature will need to be aware of this
• prefer push updates over polling
• high traffic cases will be explored later using a virtualised list
• prefer to solve persistence and remote connection concerns in main