[wp-trac] [WordPress Trac] #13307: 3.0 package size will cause memory limit problems

[WordPress Trac]

#13307: 3.0 package size will cause memory limit problems
-----------------------------+----------------------------------------------
 Reporter:  nacin            |        Owner:  nacin 
     Type:  defect (bug)     |       Status:  closed
 Priority:  highest omg bbq  |    Milestone:  3.1   
Component:  General          |      Version:  3.0   
 Severity:  blocker          |   Resolution:  fixed 
 Keywords:                   |  
-----------------------------+----------------------------------------------
Changes (by ryan):

  * milestone:  3.0 => 3.1


Comment:

 Background: We unzip in memory because the only place we can directly
 write to disk is temp space, and we have to jump through hoops to reliably
 get a place in temp to write. File operations anywhere else must be
 abstracted, which means it usually must go through ftp. otto42's
 suggestion of leveraging transports that can stream to a file is a good
 one that we should follow up on, but as he mentioned that is a 3.1 thing.
 We've learned the hard way that seemingly simple changes to transport
 setup are likely to blow up in our faces.

 There's not much more we can do here for 3.0, which goes RC soon.
 Addressing root causes will have to wait for 3.1.

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