[wp-trac] Re: [WordPress Trac] #4779: Proposal for HTTP POST and REQUEST API

[WordPress Trac]

#4779: Proposal for HTTP POST and REQUEST API
--------------------------------------------------+-------------------------
 Reporter:  darkdragon                            |        Owner:  anonymous
     Type:  enhancement                           |       Status:  new      
 Priority:  normal                                |    Milestone:  2.6      
Component:  Optimization                          |      Version:           
 Severity:  normal                                |   Resolution:           
 Keywords:  has-patch needs-testing dev-feedback  |  
--------------------------------------------------+-------------------------
Comment (by DD32):

 > I should point out that I would like to either see this ticket die or be
 implemented.
 Same here, That was the only reason i put forward a simple function, If
 the OO method wasnt going to make it, I'd at least have liked to see a
 simplistic function work its way in instead.

 > For the entire time I went with the object oriented approach I didn't
 receive a word of feedback.

 I noticed that at the time, I just hoped that it meant that no-one had
 anything against it, And that it was a nice track to follow.

 Maybe a list needs to be made for what *would* constitute a good API, and
 take it from there:
  * Single function call to retrieve a simple document
  * Automatic fallback to other methods in order of preference
  * GET/HEAD/POST fully supported and useable under each fallback
  * Able to be used by all core files without issue

 the scattered fsockopen's are working pretty well on the majority of hosts
 at present, However, it lacks Proxy support (an extra 2 lines in each
 really..), different sections of code may use a different method (ie.
 updater uses fsockopen, ping uses remote_url_open & fopen() AFAIK) which
 leads to one section working, and another not.

 Maybe some feedback from actual devs with reasons for/against the provided
 method, and/or what would need to be present in any approaches put forward

-- 
Ticket URL: <http://trac.wordpress.org/ticket/4779#comment:28>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software