[wp-hackers] Unified HTTP Request API

[Peter Westwood]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jacob wrote:
> Matt Mullenweg wrote:
>> Jacob wrote:
>>> I'm writing for input on any thoughts on the current prototyped API
>>> and thoughts on whether such an patch would be worth placing in the
>>> core of WordPress. Are any WordPress devs working on something similar?
>>
>> What you've described seems very complicated for what should be simple
>> operations, ideally a single-line function call.
>>
> Well, I wrote up a quick prototype [1] of what I mean. Not production
> quality, nor is it finished. The hard parts are in implementing the
> request method for each class.
> 
> A couple of ideas. I have implementations for GET, but I haven't wrote
> the functions for POST, however, I believe Snoopy is used for that
> purpose, so no doubt that it won't be needed, but would be super easy to
> create.
> 
> I was wondering if I should finish it and how likely that it would be
> included in to WordPress (if not, then what I could do to get it to that
> point). I'm actually more proud of this version than the last permutation.
> 
> [1] http://trac.wordpress.org/attachment/ticket/4779/http.php
> 

This looks interesting.

If we are going to develop an internal API to remove the multiple calls
littered around the code then we need to review whether or not we should
just extend snoopy or if we are going to replace it remove it completely
from being called by core code and deprecate it later.

For the core implementation we should concentrate on the 2 or 3
implementations that cover 90%+ of the install base and leave the more
esoteric ones as plugin territory.

westi
- --
Peter Westwood
http://blog.ftwr.co.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHPuIlVPRdzag0AcURAmDSAJ9LpfAM1d99d1vtkPwXLIhUMrP0bQCgv2tT
ij3sIMRDyxIFFaMcpuqNaTo=
=nOGm
-----END PGP SIGNATURE-----