Re: [PEPr] Changes in proposal for Tools and Utilities::ParamHandler
| From: | Lukas Kahwe Smith | Date: | Wed, 03 May 2006 12:34:04 +0000 |
| Subject: | Re: [PEPr] Changes in proposal for Tools and Utilities::ParamHandler | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-42435@lists.php.net to get a copy of this message | ||
bertrand Gugger wrote:
For the category question , I suggested Streams, but really , that is not easy to chose , as so many Categories , some with 1 or 2 packages , others with some 10.Yeah .. its not really about streaming .. just parameter parsing ..
You tell parameters are "string" , in some way I understand that scalars values are not checked.It essentially a compact yet readable serialize() that is optimized for the given context (GET/mod_rewrite, shell .. etc.)
If so , it's only linear input. I mean just known by the order.No. You can use the order to compact the serialize format more, since this allows you to skip the keys. But this is optional.
Anyway, I'm the first to agree pear needs some scripts to run from anywhere. In this extend , I don't ubderstand your example. It looks as only http.The first example I posted into the PEPr proposal is mod_rewrite, the second is for a shell command. We have used this for example to trigger a paramterised php shell script via a cron job. The key aspect is that this format allows you to pass in arrays. But admitedly we have put in the most work in the WWW class. For example we have not really implemented the ability to compact the serialized string for shell scripts. So maybe it will just end up being a solution for WWW .. but I think even if the current implementation is lacking for shell/email and there is no solution yet for web services for example .. this might still be something that should be done for the future. regards, Lukas