About scenarios for resource bundle storage resource path names

Resource bundles generally do not directly store the path name of the resource file, but rather hash the pathname, storing its hash-id (in order to avoid the hash conflict, it is best to do two hash, with two hash unique tag a resource file).

This not only makes the query faster, but also avoids the problem that the length of the file record structure (Entry) is not uniform due to the longer path name of the resource file.

However, if there is a need to store the path name of the resource file, you can actually find a way to implement the record resource file path name without affecting the resource bundle file entry (Entry) record structure.

Specific practices:

Take Hash-id as the system occupancy ID of 0, this hash-id is used to store a system file Systemfile (this file is to record all resource path names).

This file records all file paths that are added to the resource bundle, and then the resource file entry (Entry) in the resource bundle records the offset and length of its file path name in the system file (systemfile) separately.

Finally, this system file is added to the resource bundle like any other file, keeping in mind that its hash-id is 0.

This method adds a record to the pathname and does not alter the resource bundle much.

About scenarios for resource bundle storage resource path names