[wp-trac] [WordPress Trac] #21098: Out of memory errors in XML-RPC

[WordPress Trac]

#21098: Out of memory errors in XML-RPC
---------------------------------+------------------------------
 Reporter:  koke                 |       Owner:
     Type:  defect (bug)         |      Status:  new
 Priority:  normal               |   Milestone:  Awaiting Review
Component:  XML-RPC              |     Version:  3.4
 Severity:  major                |  Resolution:
 Keywords:  mobile dev-feedback  |
---------------------------------+------------------------------

Comment (by koke):

 Replying to [comment:9 maxcutler]:
 > The other downside to a streaming output implementation is that the
 `Content-Length` header is required by the XML-RPC spec. I don't know how
 reliant various client implementations are on that header, but it's a
 potential source of breakage.

 Yeah, that's why we went for the file based streaming on the client, since
 some servers (apache with mod_security I think) would throw errors if
 Content-Length was missing

 > As redsweater said, as a client author you have to transfer blame to the
 hosting provider. If you set request parameters that work on 90-95% of
 hosts, then you've done due diligence. The remaining 5-10% need to take it
 up with their hosting provider to get it fixed, and you can't waste
 extraordinary effort and code to cater to the outliers.

 I agree on that. I think there's no harm on looking into memory
 optimizations anyway, but as for hosting:

 * I see no memory requirements at http://wordpress.org/about/requirements/
 * Most of our error reports were hosted at Bluehost, which is one of the
 recommended hosting providers at http://wordpress.org/hosting/

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/21098#comment:10>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software