Resume Functionality

[DannyZB]

Does the class support resume functionality ?
In addition to that , can I add files from URL's instead of paths ?

[Grandt]

In short:

1. Sadly, no. Once the file is delivered or the connection is closed,
   PHP will remove the temporary data. That said, I'll have to look at what
   resume functionality entails. It is possible that if the zip files
   generated are identical, the class should be able to spool forward to
   the requested position before resuming data transfer. One caveat in
   that, would be those files that have the current timestamp as the time
   (generated content often does) and if the generated content isn't 100%
   identical to the original, the CRC and size checks will result in a
   corrupted file.
2. I honestly don't know. I'll have a look at what I actually put in it
   for loading files. I made a "multi vector" url and file loader (trying
   different methods, depending on which are available on the PHP
   installation) for my PHPePub class.

Cheers
A.Grandt

On 10-07-2014 16:06, DannyZB wrote:

Does the class support resume functionality ?
In addition to that , can I add files from URL's instead of paths ?

—
Reply to this email directly or view it on GitHub
#29.

[DannyZB]

Jumping to the next position should be easy.

The way NgxZip does it is require the CRC of all the files to allow resume - that way it makes sure the files are identical.
Then all you need to do is jump to the right position.

Second thing :
Is it possible to reach a several-KB memory footprint ?
i.e even without compression - this is just about pushing the files together as a folder

And the URL thing is vital for me.

Basically , I need a drop-in replacement for NgxZip

[Grandt]

The trick is to keep track of the crc for the files added.

I'm not entirely sure what you mean by "several-KB memory footprint"
PHPZip caches data in memory, up to a point (< 1MB), beyond which it'll
create a temp file for all of this data, from which it'll then spool the
final Zip file.

I'll have a look at the URL, but it probably won't be until tomorrow.

Cheers
A.Grandt

On 10-07-2014 18:24, DannyZB wrote:

Jumping to the next position should be easy.

The way NgxZip does it is require the CRC of all the files to allow
resume - that way it makes sure the files are identical.
Then all you need to do is jump to the right position.

Second thing :
Is it possible to reach a several-KB memory footprint ?
i.e even without compression - this is just about pushing the files
together as a folder

And the URL thing is vital for me.

Basically , I need a drop-in replacement for NgxZip

—
Reply to this email directly or view it on GitHub
#29 (comment).

[DannyZB]

tomorrow is still good

I'll give you the exact scenario:
https://www.seedr.co.il/

A user wants to fetch an entire 12GB torrent , files are stored on 3
different servers.
Data needs to be pushed the moment it is read , nothing beyond several
megabytes "stored" anywhere..

Is that how it works?

On Thu, Jul 10, 2014 at 8:11 PM, Asbjørn Grandt notifications@github.com
wrote:

The trick is to keep track of the crc for the files added.

I'm not entirely sure what you mean by "several-KB memory footprint"
PHPZip caches data in memory, up to a point (< 1MB), beyond which it'll
create a temp file for all of this data, from which it'll then spool the
final Zip file.

I'll have a look at the URL, but it probably won't be until tomorrow.

Cheers
A.Grandt

On 10-07-2014 18:24, DannyZB wrote:

Jumping to the next position should be easy.

The way NgxZip does it is require the CRC of all the files to allow
resume - that way it makes sure the files are identical.
Then all you need to do is jump to the right position.

Second thing :
Is it possible to reach a several-KB memory footprint ?
i.e even without compression - this is just about pushing the files
together as a folder

And the URL thing is vital for me.

Basically , I need a drop-in replacement for NgxZip

Reply to this email directly or view it on GitHub
#29 (comment).

Reply to this email directly or view it on GitHub
#29 (comment).

[Grandt]

That's ZipStream doing that, though it doesn't start sending the
individual files zipped data before it has it packed. Meaning if you add
a 1GB file, it'll have to store the zip file in a temp file until it's
completed zipping that one file.
It works great on many small and medium files, I've never tried it on 12GB.

Zip will build the entire Zip file in a temp file before starting to
send it. Large files may result in a timeout, which is why I came up
with the stream version.

On 10-07-2014 19:13, DannyZB wrote:

tomorrow is still good

I'll give you the exact scenario:
https://www.seedr.co.il/

A user wants to fetch an entire 12GB torrent , files are stored on 3
different servers.
Data needs to be pushed the moment it is read , nothing beyond several
megabytes "stored" anywhere..

Is that how it works?

On Thu, Jul 10, 2014 at 8:11 PM, Asbjørn Grandt
notifications@github.com
wrote:

The trick is to keep track of the crc for the files added.

I'm not entirely sure what you mean by "several-KB memory footprint"
PHPZip caches data in memory, up to a point (< 1MB), beyond which it'll
create a temp file for all of this data, from which it'll then spool
the
final Zip file.

I'll have a look at the URL, but it probably won't be until tomorrow.

Cheers
A.Grandt

On 10-07-2014 18:24, DannyZB wrote:

Jumping to the next position should be easy.

The way NgxZip does it is require the CRC of all the files to allow
resume - that way it makes sure the files are identical.
Then all you need to do is jump to the right position.

Second thing :
Is it possible to reach a several-KB memory footprint ?
i.e even without compression - this is just about pushing the files
together as a folder

And the URL thing is vital for me.

Basically , I need a drop-in replacement for NgxZip

Reply to this email directly or view it on GitHub
#29 (comment).

Reply to this email directly or view it on GitHub
#29 (comment).

—
Reply to this email directly or view it on GitHub
#29 (comment).

[DannyZB]

Is there a way to pack while sending ? That would save the huge overhead of
temp files and memory usage
On Jul 10, 2014 8:22 PM, "Asbjørn Grandt" notifications@github.com wrote:

That's ZipStream doing that, though it doesn't start sending the
individual files zipped data before it has it packed. Meaning if you add
a 1GB file, it'll have to store the zip file in a temp file until it's
completed zipping that one file.
It works great on many small and medium files, I've never tried it on 12GB.

Zip will build the entire Zip file in a temp file before starting to
send it. Large files may result in a timeout, which is why I came up
with the stream version.

On 10-07-2014 19:13, DannyZB wrote:

tomorrow is still good

I'll give you the exact scenario:
https://www.seedr.co.il/

A user wants to fetch an entire 12GB torrent , files are stored on 3
different servers.
Data needs to be pushed the moment it is read , nothing beyond several
megabytes "stored" anywhere..

Is that how it works?

On Thu, Jul 10, 2014 at 8:11 PM, Asbjørn Grandt
notifications@github.com
wrote:

The trick is to keep track of the crc for the files added.

I'm not entirely sure what you mean by "several-KB memory footprint"
PHPZip caches data in memory, up to a point (< 1MB), beyond which it'll
create a temp file for all of this data, from which it'll then spool
the
final Zip file.

I'll have a look at the URL, but it probably won't be until tomorrow.

Cheers
A.Grandt

On 10-07-2014 18:24, DannyZB wrote:

Jumping to the next position should be easy.

The way NgxZip does it is require the CRC of all the files to allow
resume - that way it makes sure the files are identical.
Then all you need to do is jump to the right position.

Second thing :
Is it possible to reach a several-KB memory footprint ?
i.e even without compression - this is just about pushing the files
together as a folder

And the URL thing is vital for me.

Basically , I need a drop-in replacement for NgxZip

Reply to this email directly or view it on GitHub
#29 (comment).

Reply to this email directly or view it on GitHub
#29 (comment).

Reply to this email directly or view it on GitHub
#29 (comment).

Reply to this email directly or view it on GitHub
#29 (comment).

[Grandt]

There is, I haven't figured out the specifics yet, as I haven't figured
out how to read from the temp file I'm zipping into while adding more
data. And I haven't figured out how to make PHP multi task.

On 10-07-2014 19:24, DannyZB wrote:

Is there a way to pack while sending ? That would save the huge
overhead of
temp files and memory usage
On Jul 10, 2014 8:22 PM, "Asbjørn Grandt" notifications@github.com
wrote:

That's ZipStream doing that, though it doesn't start sending the
individual files zipped data before it has it packed. Meaning if you
add
a 1GB file, it'll have to store the zip file in a temp file until it's
completed zipping that one file.
It works great on many small and medium files, I've never tried it
on 12GB.

Zip will build the entire Zip file in a temp file before starting to
send it. Large files may result in a timeout, which is why I came up
with the stream version.

On 10-07-2014 19:13, DannyZB wrote:

tomorrow is still good

I'll give you the exact scenario:
https://www.seedr.co.il/

A user wants to fetch an entire 12GB torrent , files are stored on 3
different servers.
Data needs to be pushed the moment it is read , nothing beyond
several
megabytes "stored" anywhere..

Is that how it works?

On Thu, Jul 10, 2014 at 8:11 PM, Asbjørn Grandt
notifications@github.com
wrote:

The trick is to keep track of the crc for the files added.

I'm not entirely sure what you mean by "several-KB memory
footprint"
PHPZip caches data in memory, up to a point (< 1MB), beyond
which it'll
create a temp file for all of this data, from which it'll then
spool
the
final Zip file.

I'll have a look at the URL, but it probably won't be until
tomorrow.

Cheers
A.Grandt

On 10-07-2014 18:24, DannyZB wrote:

Jumping to the next position should be easy.

The way NgxZip does it is require the CRC of all the files to
allow
resume - that way it makes sure the files are identical.
Then all you need to do is jump to the right position.

Second thing :
Is it possible to reach a several-KB memory footprint ?
i.e even without compression - this is just about pushing the
files
together as a folder

And the URL thing is vital for me.

Basically , I need a drop-in replacement for NgxZip

Reply to this email directly or view it on GitHub

#29 (comment).

Reply to this email directly or view it on GitHub
#29 (comment).

Reply to this email directly or view it on GitHub
#29 (comment).

Reply to this email directly or view it on GitHub
#29 (comment).

—
Reply to this email directly or view it on GitHub
#29 (comment).