php|tek PEAR/phar/Pyrus talk slides

(30)

Do you develop a website? It is infinitely better to synchronize live and development sites using the PEAR Installer

(25)

doing the PEAR thing

(19)

Using PEAR 1.4.0 to install PEAR packages on a remote host

(19)

phpDocumentor and __get/__set/__call - give us your ideas (RFC)

(17)

Syndicate This Blog

RSS 0.91 feed

RSS 1.0 feed

RSS 2.0 feed

ATOM 0.3 feed

ATOM 1.0 feed

RSS 2.0 Comments

Powered by

Serendipity PHP Weblog

Thursday, May 29. 2008

I've had a few slide requests, so here is a link to the pdf of my slides that Sean Coates put up on the phparch site

http://tek.phparch.com/mats/slides/greg_beaver-pear_phar.pdf

Posted by Greg Beaver in PHP at 09:46 | Comments (3) | Trackbacks (0)

Trackbacks

Trackback specific URI for this entry

No Trackbacks

Comments

Display comments as (Linear | Threaded)

Hi Greg!
Thanks for this info about phar and nice extension. I've started for testing and usage phar.

Is it possible to use phar with non-file-based storage?

For example:

$a = new Phar('any_storage://package.phar.tar');

and also in includes or need real file for reading and includes? Only temp-files way?

If it possible and not very slow please add such features that allow work with alternative storages such as memory, string, custom(for DB) and so on

#1 dan on 2008-09-05 11:07 (Reply)

Hi Dan,

Phar only works with file-based storage for several reasons. Although streams could be supported relatively easily, this could introduce an unnecessary security risk. For instance:

Phar is explicitly enabled to work with only local files, remote is never supported.

It's really not good to use a dynamically created phar in the same process, you should only ever use one that was created separately.

#1.1 Greg Beaver (Homepage) on 2008-09-05 16:34 (Reply)

Hi, Greg,

Well, I understand that write permissions really danger in web applications.

I plan to use phars as tar-packages-libraries in basically (not web-executable). This is a very suitable alternative for set_include. How about performance in this case? My library in phar will extracted once or per-request?

Of course, that creating phar and include phar will be in separated processes. But I would like to keep phars not only in filesystem but in memory or database for later using.

This requires at least two basic approaches:

- copy phar.tar from alternative storage to temp-file-storage
- include 'phar:///temp/storage/lib.phar.tar'

or another:

- create stream-wrapper for phar that can load phar from memory, string or db
- include 'mywrapper:///memstorage/lib.phar.tar'

#1.1.1 Dan on 2008-09-06 03:49 (Reply)

Add Comment

Name
Email
Homepage
In reply to
Comment	Standard emoticons like :-) and ;-) are converted to images. E-Mail addresses will not be displayed and will only be used for E-Mail notifications To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly. Enter the string from the spam-prevention image above: BBCode format allowed You can use [geshi lang=lang_name [,ln={y\|n}]][/lang] tags to embed source code snippets
	Remember Information? Subscribe to this entry
Submitted comments will be subject to moderation before being displayed.