librematch:design:collector:parsing

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
librematch:design:collector:parsing [2022-10-27 22:53] – ↷ Page moved from librematch:collector:parsing to librematch:design:collector:parsing simonsanlibrematch:design:collector:parsing [2022-10-28 01:30] (current) nimda
Line 9: Line 9:
      
   * prioritization \\ Some data is the foundation for real-time information that we deliver to users of our API (state changes of lobbies, e.g. ongoing matches, and leaderboard rankings). \\ This data should fill 'sorted sets' or the Pub/Sub-Message bus from Redis.   * prioritization \\ Some data is the foundation for real-time information that we deliver to users of our API (state changes of lobbies, e.g. ongoing matches, and leaderboard rankings). \\ This data should fill 'sorted sets' or the Pub/Sub-Message bus from Redis.
 + 
 +  * conversion \\ For the localization data, we need to query data from the Relic Link API and convert it to the FTL (Fluent Translation) file format. 
  
  
  • librematch/design/collector/parsing.1666904022.txt.gz
  • Last modified: 4 years ago
  • by simonsan