Comments on Profile Post by willies952002

  1. willies952002
    willies952002
    that arose when signatures were being generated a bit too fast, making it so they would tend to generate with at least the face missing, and flooding my error log with message. For that reason, I have decided to discontinue J.A.E.M.C.S.G. Version 1 and start Development of Version 2, which will be aimed at better performance of the generator as well as the back-end when a signature is requested from (cont. below)
    Aug 20, 2017
  2. willies952002
    willies952002
    the system to be generated on-the-fly.

    I hope this is understandable and that you're now all looking forward to Version 2 :)
    Aug 20, 2017
  3. JackBiggin
    JackBiggin
    TIL you weren't generating them on the fly. The (currently broken >_>) EMC Signature Generator just stores everything in a giant hash and generates each time with a 5 minute cache.
    Aug 20, 2017
  4. willies952002
    willies952002
    Technically the signatures were generated on-the-fly, but the parts, such as the head and merged background (background + frame) were stored in a cache. Each request would then take the background, put the head on it, then populate the text. (cont. below)
    Aug 20, 2017
  5. willies952002
    willies952002
    The final image wasn't being cached as to reflect any changes to status, such as group and online/offline, near instantly, where the only factor which would make it not instant was the Empire "Public" API.
    Aug 20, 2017
  6. JackBiggin
    JackBiggin
    Definitely worth caching full image then for at least the length of the API's cache. IIRC I also store base64 head data and group in DB, and only update once every 250ish pageloads to keep stuff fast
    Aug 20, 2017