SL24W45: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
** Cleanup bootup-sequence of ChunkliService and Server after conversion | ** Cleanup bootup-sequence of ChunkliService and Server after conversion | ||
** Add safety-checks to differentiate between PlayerId,ServerId, Fixed consoleUuid | ** Add safety-checks to differentiate between PlayerId,ServerId, Fixed consoleUuid | ||
* Implement Server2Server websocket communication | |||
** Use one-time-token for establishing the connection | |||
** | |||
* Make sure we have at least: | |||
** Automatic reconnect | |||
** Simple Message for very short disconnects | |||
** logging | |||
** targeted responses (render client feedback on finished jobs) | |||
** Lookup if STOMP gives us an idea of the WS reconnect/queue impl | |||
** Come up with a way to propose render jobs and let the renderclients fight for the job | |||
*** If a job is not done within <15 seconds consider it unfinished and allow grabbing it again | |||
*** | |||
Latest revision as of 20:17, 10 November 2024
- Implement NamedUid as parent interface for PlayerId and ServerId
- Cleanup bootup-sequence of ChunkliService and Server after conversion
- Add safety-checks to differentiate between PlayerId,ServerId, Fixed consoleUuid
- Implement Server2Server websocket communication
- Use one-time-token for establishing the connection
- Make sure we have at least:
- Automatic reconnect
- Simple Message for very short disconnects
- logging
- targeted responses (render client feedback on finished jobs)
- Lookup if STOMP gives us an idea of the WS reconnect/queue impl
- Come up with a way to propose render jobs and let the renderclients fight for the job
- If a job is not done within <15 seconds consider it unfinished and allow grabbing it again