Re: PEAR2_Http_Request / HTTP_Request2
| From: | David Coallier | Date: | Tue, 11 Sep 2007 18:39:16 +0000 |
| Subject: | Re: PEAR2_Http_Request / HTTP_Request2 | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-47996@lists.php.net to get a copy of this message | ||
On 9/11/07, Christian Schmidt <pear.php.net@chsc.dk> wrote:
> Joshua Eichorn wrote:
> > Just a heads up for anyone who is interested, there is a
> > PEAR2_Http_Request class in PEAR2 SVN.
> Cool.
>
> > Its a driver/adapter based model that lets you make requests directly
> > with sockets, with streams, with curl, or with pecl_http (all the
> > adapters don't work right now).
> What is the purpose of all these adapters instead of just making one
> well-tested implementation that works everywhere (e.g. socket based)?
>
Some people configure with sockets, some people don't.
Some people configure with curl, some people don't.
Some may want the pecl_http but with their current implementation,
thus same API or simplicity.
Also preference, some people swear only by curl, some others by streams.
What about all the adapters well tested ? Everyone has a fit to their shoe.
It's like saying, what is the purpose of MDB2's adapters when mysqli
is well tested. Some may use curl simply for consistency of their
code, maybe they have some custom built curl that does something
special on each of their requests. Anything can happen really. What is
wrong with having the choice without the loss of speed ?
I think that if one doesn't want to use the curl/streams/pecl_http he
can simply install the core and socket drivers. Same goes for all the
other adapters/drivers.
>
> Christian
>
> --
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
David Coallier,
Founder & Software Architect,
Agora Production (http://agoraproduction.com)
51.42.06.70.18