Skip to content

Reduce image calls to server #1

@blitzmann

Description

@blitzmann

When displaying an LP Store, there may be hundreds of offers, each having their own icon. However, the icons are the same against many items, even if the typeID of the item is unique. The purpose of this issue is to address making hundreds of calls to the server to get the same icon.

Currently, icons are called via typeID to the EVE servers. This will suffice until I can get my owner image loader in place. See thoughts below.

(old notes, must refine)

At this moment, icons are called via typeID_size.png. I need this to turn into iconID_size.png. In the community toolkit, CCP releases a few YAML files. In typeIDs.yaml it gives reference to an icon ID, and in iconIDs.yaml it shows the actual filename (or part of the filename) of the icon.

The filenames are in a #1_64_#2.png format, where I assume the 64 is the size. The iconID gives the file ID in the #1_#2 format which corresponds to the filename of the icon without the size information.

The icons also do not have the meta indicator, so that must be added.

Possible solution:
Redirect /img/ID_SIZE_MOD.png to a processing page. ID will be the icon id, size will be either 32 or 64, and mod will be a flag for modifiers to the image (meta tag). Assemble the images together appropriately and send output as PNG image with a long cache.

How do we find the iconID of each offer? Possibly create a singleton class that reads the YAML file once and makes lookups of the icon ID, returning the processed iconID. Or perhaps create a SQL table that links typeID to iconID (this would require preprocessing).

Info:

Tech II meta filename: 73_16_242
Faction meta filename: 73_16_246

(this should be all that is needed for lpDatabase, as it doesn't work with officer / tech3 / other metas).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions