![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
kriegorSomehow I've only known about compression algorithms in the vaguest possible sense until this week.
I still wish I could get a byte-by-byte animation of it, but I think I get the gist of how the library is intended to be used-- load up compressed data into one buffer, decompress it into another buffer (or directly to disk, though I understand this many tiny disk writes can get technically expensive).
If the information left in the 'to decompress' buffer is too partial to continue, or is fully empty, load more. (This case may be impossible, and I may be overthinking it; this is why I would like a byte-by-byte visual so I can see if I'm misunderstanding the way the deflate alg works.) Keep doing this until there's nothing left. (This 'overthinking' leaves me with more questions - for one, is it possible to do this byte-by-byte, or is there a minimum buffer size? Basic likely-misunderstandings that could again be alleviated visually)
On that note, I now understand completely why loading PRAY data especially for large files in c2e is laggy as shit; it doesn't store the 'agent metadata' anywhere after it's been unpacked, and is essentially allocating RAM for and decompressing the entire file just to get at a couple header bits. (And 1999 is a bit early for thoughtful multithreading)
It's nice to read docs for such a sober specification without it being totally dry.
Theoretically I'd like to get said library working today but I have to go for groceries and have no data on how foggy I may be when I get home; really wish I had the affordance to take a caffeine tolerance break. All that needs to be done is to 'apply' it to a byte buffer I'm already reading, however my still-extant questions make me sort of freeze up when I look at the problem (it's a couple of nested loops deep) as without this information I'm prone to further unnecessary complication. I don't really do well with unanswered questions or unclear behavior.
I still wish I could get a byte-by-byte animation of it, but I think I get the gist of how the library is intended to be used-- load up compressed data into one buffer, decompress it into another buffer (or directly to disk, though I understand this many tiny disk writes can get technically expensive).
If the information left in the 'to decompress' buffer is too partial to continue, or is fully empty, load more. (This case may be impossible, and I may be overthinking it; this is why I would like a byte-by-byte visual so I can see if I'm misunderstanding the way the deflate alg works.) Keep doing this until there's nothing left. (This 'overthinking' leaves me with more questions - for one, is it possible to do this byte-by-byte, or is there a minimum buffer size? Basic likely-misunderstandings that could again be alleviated visually)
On that note, I now understand completely why loading PRAY data especially for large files in c2e is laggy as shit; it doesn't store the 'agent metadata' anywhere after it's been unpacked, and is essentially allocating RAM for and decompressing the entire file just to get at a couple header bits. (And 1999 is a bit early for thoughtful multithreading)
It's nice to read docs for such a sober specification without it being totally dry.
Theoretically I'd like to get said library working today but I have to go for groceries and have no data on how foggy I may be when I get home; really wish I had the affordance to take a caffeine tolerance break. All that needs to be done is to 'apply' it to a byte buffer I'm already reading, however my still-extant questions make me sort of freeze up when I look at the problem (it's a couple of nested loops deep) as without this information I'm prone to further unnecessary complication. I don't really do well with unanswered questions or unclear behavior.
