In about a month or so, i'll start work on an extension implementing a file format which allows for bundling all resources related to a app (including
I'd very much recommend using an already existing file format, e.g. PEAR::PHP_Archive (uses tar) or something based on zip.
The disadvantage over Tar or other archive formats is that they are standardized, and have lots of available tools which can be used to
The advantage of a proven format and being able to use standard tools are priority #1 IMHO.
manipulate them. The advantage over other formats is that the resources can be used in-place using a custom PHP stream (i.e. run in place - no unzipping). Of course, anything can be stuffed into the files, so if
Considering how fast current computers are and based on the fact that wrappers for current archive format can already hide the unzipping step I'd resist the temptation to create yet-another-archive-format.
My 2 Rappen, - Chris
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
