[wp-trac] [WordPress Trac] #16236: Method to stream file downloads in HTTP API, to reduce update memory footprint

[WordPress Trac]

#16236: Method to stream file downloads in HTTP API, to reduce update memory
footprint
----------------------------+-----------------------------
 Reporter:  markjaquith     |       Owner:
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  Future Release
Component:  HTTP            |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  3.2-early       |
----------------------------+-----------------------------

Comment (by sivel):

 Replying to [comment:6 dd32]:
 > A few other thoughts:
 > - We should probably let the caller specify the destination folder AND
 filename, save the class guessing where to put the file.
 I wonder about allowing the user to specify the destination directory.  As
 with the uploads dir we enforce that it must be relative to the wp-content
 dir.  Perhaps if specified we force it to be relative to wp-content.
 Should we also make it clear that the directory should exist first?  Not
 sure if we want to go about attempting to make the directory or not.
 > - The return could be modified to have headers, body(empty - for
 backcompat purposes), and (optionally) a filename/path field for when it's
 been saved
 Should we introduce a new section to the return?  Or just add it to the
 'response' section?  Currently headers should be populated, and an empty
 body should be returned.

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