[wp-hackers] Unified HTTP Request API

[Jacob]

Peter Westwood wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>   
> 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-----
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>   
Yes, I was thinking about that, having three and leaving the rest as 
something else. It would be even be possible to build a plugin that 
interfaces Snoopy for a backwards compatibility plugin. Since the filter 
is first and all of the other checks last, it is completely possible to 
forego the default checks and replace it with a plugin.

I'm actually not looking to replace Snoopy and looking at it, I couldn't 
extend it without refactoring large portions. I'm not sure what uses it 
(plugins, core), but I can do a search and see.

-- 

Jacob Santos

http://www.santosj.name - blog
http://wordpress.svn.dragonu.net/unittest/ - unofficial WP unit test suite.

Also known as darkdragon and santosj on WP trac.