[wp-trac] [WordPress Trac] #13777: Consolidate WP_Http argument processing into a single class
WordPress Trac
wp-trac at lists.automattic.com
Sun Mar 27 01:00:51 UTC 2011
#13777: Consolidate WP_Http argument processing into a single class
-----------------------------------------+--------------------------
Reporter: jacobsantos | Owner: jacobsantos
Type: enhancement | Status: closed
Priority: low | Milestone:
Component: HTTP | Version: 3.0
Severity: minor | Resolution: wontfix
Keywords: has-patch 2nd-opinion close |
-----------------------------------------+--------------------------
Changes (by jacobsantos):
* status: reopened => closed
* resolution: => wontfix
Comment:
Replying to [comment:10 dd32]:
> Then my opinion remains the same, The Core HTTP API should require users
call the handler (WP_HTTP) rather than subclasses directly, they should
all have the same support on every system and if they don't, then the
WP_HTTP handler should not allocate a request to one.
>
> I realise this may differ from your original intentions of the HTTP API,
but my opinion is being based on what I feel is best for WordPress
developers AND users as a whole; that is, that everything should "just
work" and a plugin relying upon a certain transport does not fit that idea
to me.
Okay, I can accept this reason. Whether or not I agree, at least it
explains the direction for someone wondering why it is this way.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/13777#comment:12>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list