my question rises from a thought I had about my app:
I'd like to add a lot of sound files (around 5000, but they could be more) and I am worried that I would eventually reach some maximum number of files allowed
cap: see here https://stackoverflow.com/a/2652238/20463613
My first thought was to split them in subdirectories, but I wonder if there is a better way to handle that which might even be of easier maintenance for the future and "download friendly".
If I could "pack" like tarball my sound files I will have to handle only one "soundpack" file, and I could easily have this single file available as "additional downloadable content" for the users who are running low on storage space. (my app is less than 10mb, but with sounds it goes up to 50mb and counting).
Unfortunately my knowledge stops here:
Do you think it's worth thinking about this potential issue or I am just being too much pessimistic?
If I am making sense: how could I build a pack of files, keeping an index, so that when my app needs "SOUND00345" it can read directly this sound from the soundpack file based on its index? I guess that this is almost the same that the filesystem does, so maybe I am just thinking about redoing something that already is taken care of..
I've found an untar pure lua library here: https://github.com/mimetic/tar.lua
which works fine in gideros, but the only way to extract a single file from the archive is to parse it all until it finds the file/files inside the archive, and this might be counterproductive if the archive is big because it certainly takes time..
Any idea/suggestion is appreciated