Review Request 128369: Handle multiple gzip streams in a single file
Martin Tobias Holmedahl Sandsmark
martin.sandsmark at kde.org
Mon Jul 4 22:02:40 UTC 2016
> On July 4, 2016, 9:39 p.m., David Faure wrote:
> > src/kgzipfilter.cpp, line 331
> > <https://git.reviewboard.kde.org/r/128369/diff/1/?file=471082#file471082line331>
> >
> > This is where you could add something like
> > if (avail_in < 10) {
> > return Ok; // come back when we have more
> > }
> > if (readHeader()) { ... }
> > no?
Then we'd need to somehow save what we currently have in the buffer and concatenate with the next. I tested this with setting BUFFER_SIZE to 29 bytes (the stream in Sune's test file is 28 bytes).
I don't really think handling an uncompressed stream after the compressed one is something we really need to care about, so just ignoring the header I think is good enough for now, or?
- Martin Tobias Holmedahl
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/128369/#review97103
-----------------------------------------------------------
On July 4, 2016, 9:57 p.m., Martin Tobias Holmedahl Sandsmark wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/128369/
> -----------------------------------------------------------
>
> (Updated July 4, 2016, 9:57 p.m.)
>
>
> Review request for KDE Frameworks and Sune Vuorela.
>
>
> Repository: karchive
>
>
> Description
> -------
>
> This assumes that the split between the streams is in the current buffer, though.
>
>
> Diffs
> -----
>
> autotests/kfiltertest.cpp 4408dbe
> src/kcompressiondevice.cpp d6ecebd
> src/kgzipfilter.cpp 27a6d99
>
> Diff: https://git.reviewboard.kde.org/r/128369/diff/
>
>
> Testing
> -------
>
> The unit test now passes.
>
>
> Thanks,
>
> Martin Tobias Holmedahl Sandsmark
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20160704/278ab796/attachment.html>
More information about the Kde-frameworks-devel
mailing list