Re: Re: [PEPr] Comment on Web Services::Services_Digg
| From: | Joe Stump | Date: | Sun, 22 Apr 2007 18:54:50 +0000 |
| Subject: | Re: Re: [PEPr] Comment on Web Services::Services_Digg | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-46384@lists.php.net to get a copy of this message | ||
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
1.) I'm the lead of Net_Curl. I can package a Net_Curl2. There are some BC incompatible changes I've been meaning to do for a long time. So that takes care of that. Jausions and I have been talking about deprecating it in favor of HTTP_Request as well. I'd be interested in helping out with the HTTP_Request2 as well.
2.) David, et al, there is a fairly comprehensive suite of tests in Services_Digg. Feel free to use them to debug HTTP_Request.
3.) I still don't see how this effects Services_Digg (PEAR_Error will be converted ASAP to PEAR_Exception) as HTTP_Request isn't available in any tangible way to the users of Services_Digg. I can switch out to Net_Curl2 or HTTP_Request2 at any point in the future without breaking BC on Services_Digg. So, while I do see the point of the RFC, I don't see how it really applies in this situation.
- --Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFGK698h0MUGpYY9OQRAuipAJ9jX1jc5zeppGiuTBnl2oeI2JFKCwCfcYSm
ucgBByn9FXLvrxc25Q1cQCE=
=xQix
-----END PGP SIGNATURE-----