Skip to content
This repository was archived by the owner on Nov 7, 2022. It is now read-only.
This repository was archived by the owner on Nov 7, 2022. It is now read-only.

Provide automatic Skin and Cape caching #6

@boomboompower

Description

@boomboompower

Skins in the cache should not stay forever. SkinChanger V2 introduced a skin cache which never automatically clears, V3 can feature one that does.

The implementation of manual clearing should stay, however automatic cache cleaning is definitely something which would benefit users. Users should be able to choose caching times, or disable the cache clearing method completely.


General implementation

  • Create system which saves items in a cache
  • When an item is requested the cache will be checked first, if the item exists in the cache it should be retrieved
  • Cache should expire after a certain period of time (Configurable??)
  • Cache should automatically cause items to expire (see Recommended steps)

Recommended steps

  • On preInit, scan all caches on a separate thread
  • Delete any caches which are found to be expired.

And also when a resource is queried

  • Scan its cache
  • Delete it if it has expired

Metadata

Metadata

Assignees

No one assigned

    Labels

    in progressThis feature is actively being worked onneeds testingA new feature has not been tested

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions