[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):

 > Add another parameter which adds a few other options, one of which for
 what HTTP version to send, however I must admit version 1.0 is a lot
 easier to handle.
 I'm not up to speed with the HTTP 1.1 spec, Content-Encoding:
 deflate/chunked/etc just confuse me from a client perspective. It'd be
 nice to support gzipped data if possible though i guess.

 > If $headers is not an array, then it will be cast to an array. I would
 rather like this to be a string also. If that is the case, then other
 handling can be done.

 wp_parse_args() i believe? Yeah, That'd be a better option actually.

 >The data will not always be URL encoded content ..[snip].. If I send XML,
 I don't want to have to hack around the current implementation.

 Thats handled allready, Pass a Array and its converted to a URL encoded
 query string. Pass a string and its assumed you know what you want to
 pass, so it'll post the exact Serialized data or XML. (Unless i've
 stupidly done something i've not noticed?)

 > Your current fsockopen does not handle redirection correctly and leaves
 that as an exercise for the user. ..[snip]

 Point taken, It would be best to follow a certain ammount of redirects
 like some of the WP functions do.

 > There is a typo in the documentation
 oops, thanks for noting that :)

 > I would rather the dev team accept the object oriented approach
 I'd like to see something thats useable by all people accepted. I have a
 feeling one of the reasons the OO one hasnt been used so far, is that it
 *may* be seen to by some as being a more complicated option that what
 currently exists.

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