read my reply to Christian. as i mentioned, i'm working on another project which already has infrastucture for dealing with similar issues. i simply noticed that it could be adapted for the PAR/PHAR idea. IOW, the extension will be written whether or not we do the implement web archives.
BTW, i gave your blog only a cursory glance, so i can't comment in depth. however, i will say that the format addresses your issue of not having to unpack. the file is memory mapped and cached, so all resources are available without file operations beyond the initial open resource types are string, int, arrays (numerically indexed), tables (hashes of any other type), utf16 string and binary (arbitrary sized). resource fallback is standard (eg. /path/to/resource/en_US/ -> /path/to/resource/en/ -> root )
----- Original Message ----- From: "Jeff Moore" <[EMAIL PROTECTED]>
To: "l0t3k" <[EMAIL PROTECTED]>
Cc: <internals@lists.php.net>
Sent: Tuesday, March 15, 2005 7:10 PM
Subject: Re: [PHP-DEV] Re: par/phar/jar (was zend_stream_fixup)
On Mar 10, 2005, at 9:59 PM, l0t3k wrote:
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
PHP source, localized strings, gifs, byte-code from BCompiler etc). the
format has an heirarchical internal structure and allows for introspection
and fallback.
You might consider looking at the concept of bundles from Mac OS X:
http://developer.apple.com/documentation/CoreFoundation/Conceptual/ CFBundles/index.html
Bundles aren't a file format, but rather a directory structure, a set of naming conventions, and an API that provides these capabilities on the standard file system.
On OS X, the finder makes bundles opaque to the user. In PHP, this could be done with a standard format such as tar or zip.
I wrote about this some here:
http://www.procata.com/blog/archives/2004/11/24/installing-web- applications/
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
