Re: [PEPr] +1 for Web Services::Services_oEmbed
| From: | Joshua Eichorn | Date: | Mon, 27 Oct 2008 18:00:38 +0000 |
| Subject: | Re: [PEPr] +1 for Web Services::Services_oEmbed | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-50931@lists.php.net to get a copy of this message | ||
David Jean Louis wrote:
Also I think your design is going to start hitting snags when you look at the various options for making requests. pecl_http and curl can both do a lot of the message parsing for you and you want to use them if possible since they are a lot faster then anything we can write in php. (see http://us.php.net/manual/en/class.httpmessage.php, http://us.php.net/manual/en/class.httpquerystring.php, http://us.php.net/manual/en/function.http-parse-headers.php, http://us.php.net/manual/en/function.http-parse-message.php, etc) It may make the most sense just follow the desgin of pecl http and just add enough api around things to easily switch backends, and add in any missing features. -joshOk, as promised here's the work I've done so far on HTTP_Request2: http://code.google.com/p/izi-sandbox/source/browse/#svn/trunk I did a quick once over. I would move the Response codes and http method constants to your common code since they are likely to be useful outside of requests/responses.Ok. I'll try to finalize the parts I've started so far, and I will post them somewhere so you can check it out and move on setting things up.Thanks, HTTP_Request2 is long overdue, hope this time we'll be able to come up with something. :]