Tobias Schlitt [2004-06-14 05:06 UTC]Wow! Looks like a cute idea. I like that! :)
Alan Knowles [2004-06-14 05:35 UTC]looks like
Archive_Tar_Stream (maybe even included with the Archive Tar package)
would probably be more generic.
should really just look in the include path? for tar.tgz ?
Davey Shafik [2004-06-14 07:53 UTC]Alan Knowles Wrote:
> looks like
> Archive_Tar_Stream (maybe even included with the Archive Tar package)
> would probably be more generic.
> should really just look in the include path? for tar.tgz ?
This is not the case, the point of the script is that it allows you to call the archive containing all your application directly. i.e. http://example.org/index.phar - you could then have the phar_default.php (you will be able to specify this file when I make the creator) check the $_SERVER['PATH_INFO'] to serve a file directly from it.
Stephan Schmidt [2004-06-14 08:38 UTC]Shouldn't this be Stream_Tar, or what is the difference to a normal stream wrapper?
Furthermore I'm missing directory support.
Klaus Guenther [2004-06-14 10:59 UTC]This proposal looks very interesting. However, I would suggest calling it File_Phar. Before the 1.0 release, it should have the basic features of the jar files implemented (e.g., compression, encryption, etc.). Don't know how easy encryption will be to implement. But I suppose if you only decrypt into private variables (php5 style), it will be difficult (without modifying the class) to access the decrypted files.
All in all, it will be a nice way to distribute an application.
Also sounds like a nice entry for the Zend or dotgeek competitions - provided you make it php5 only ;-)
Jan Lehnardt [2004-06-14 11:42 UTC]what about a .phaz format that gzips or bzip2s the file. You're adding a stream filter anyways, so you can stack a zlib filter on top, no?
Cool Idea though!