SL21W41: Difference between revisions

From ETM
Jump to navigation Jump to search
(Created page with "◄ SL21W40 | SL21W42 ►")
 
No edit summary
Line 1: Line 1:
[[SL21W40|◄ SL21W40]] | [[SL21W42|SL21W42 ►]]
[[SL21W40|◄ SL21W40]] | [[SL21W42|SL21W42 ►]]
<br />
* Cleanup Week 2
** Completely remove Desktop-special case as a screen, use dynamically created ScreenModel internally to reduce complexity
*** Got rid of most of the special caching / update flags for desktop this way
*** Code reduction as the general purpose cache now works nicely
*** '''Add a quick board comparison/equality check by comparing screen-size first (+ tile element count second)? Needed? The BoardHash should do this already right?'''
* Nils intro to Kadi / Chunkli design
** '''General setup of Stasi-Plugin, based on Chunkli Api'''
*** '''Think/Test persistence layer'''
*** '''Make sure we respect shulker boxes in some way?'''
*** '''95% of data is archival data mostly? Important is mostly just worldchanges ~7 days + chat ~3 month; rest can be slow / compressed?'''
*** '''Most likely PostgreSQL + time-series => Timescale db? on an external logging server with batched inserts?'''

Revision as of 14:22, 16 October 2021

◄ SL21W40 | SL21W42 ►


  • Cleanup Week 2
    • Completely remove Desktop-special case as a screen, use dynamically created ScreenModel internally to reduce complexity
      • Got rid of most of the special caching / update flags for desktop this way
      • Code reduction as the general purpose cache now works nicely
      • Add a quick board comparison/equality check by comparing screen-size first (+ tile element count second)? Needed? The BoardHash should do this already right?
  • Nils intro to Kadi / Chunkli design
    • General setup of Stasi-Plugin, based on Chunkli Api
      • Think/Test persistence layer
      • Make sure we respect shulker boxes in some way?
      • 95% of data is archival data mostly? Important is mostly just worldchanges ~7 days + chat ~3 month; rest can be slow / compressed?
      • Most likely PostgreSQL + time-series => Timescale db? on an external logging server with batched inserts?