Hey Shaon!
I’ve been making some progress with my extension for WPDM. I’ve gotten the integration about halfway there! I’m having some issues now with ZipArchive, and I was hoping I could bounce some ideas off you.
I’m working with a massive file/Folder-Structure for my Download Package. It’s over 6,500 files, 533 folders, and is 1.21gb or so uncompressed. My script works beautifully on smaller f/F-structures when I test it, but the entire Package is still too much. I first began hitting problems with the file handler limit, or u limit, and solved that. But now, it appears I have no conventional way around my php page time outs – it’s a Shared Hosting server problem. GoDaddy doesn’t allow me to set the timeout too far, and I can’t set ignore_user_abort either. Here is what I’ve done thus far:
-increased php mem to 1024mb
-reworked script to build archive on disk as local temp first, instead of building in memory
-created a method to ($zip->close; $zip->reopen) archive every 255 addfiles; to fix u limit (file handler limit) bug
-coupled addFromString(contents) with addFile(file) [somehow this gave me better results]
I think I’ve reached the limit of what I can do conventionally to solve the PHP-timeout on Massive f/F-structures. So, now I’m going to pursue unconventional means. I’m developing an idea to stream the ziparchive() operation to the browser, and then redirect to itself after (X) amount of loops. I’m planning on trying out ftell() and fseek(), and maybe an iFrame to accomplish this.
Paul Duncan has written a ZipArchive extension that seems to do this: http://pablotron.org/software/zipstream-php/
However, his code is much more extensive and heavy than I would like. I hope to develop a cleaner way to do it.
How familiar are you with this situation? Do you have any tricks already up your sleeve to counter PHP-timeout errors like this? Or perhaps any tips on streaming ZipArchive? I’ll begin work on streaming the script now, I’ll appreciate input of any kind.
Thanks Shaon!
