Message125923
| Author |
v+python |
| Recipients |
r.david.murray, v+python |
| Date |
2011年01月10日.20:17:18 |
| SpamBayes Score |
2.782332e-05 |
| Marked as misclassified |
No |
| Message-id |
<1294690640.72.0.944923816111.issue10879@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
R. David said:
However, I'm not clear on how that helps. Doesn't FieldStorage also load everything into memory?
I say:
FieldStorage in 2.x (for x <= 6, at least) copies incoming file data to a file, using limited size read/write operations. Non-file data is buffered in memory.
In 3.x, FieldStorage doesn't work. The code that is there, though, for multipart/ data, would call email to do all the parsing, which would happen to include file data, which always comes in as part of a multipart/ data stream. This would prevent cgi from being used to accept large files in a limited environment. Sadly, there is code is place that would the copy the memory buffers to files, and act like they were buffered... but process limits do not care that the memory usage is only temporary... |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年01月10日 20:17:20 | v+python | set | recipients:
+ v+python, r.david.murray |
| 2011年01月10日 20:17:20 | v+python | set | messageid: <1294690640.72.0.944923816111.issue10879@psf.upfronthosting.co.za> |
| 2011年01月10日 20:17:18 | v+python | link | issue10879 messages |
| 2011年01月10日 20:17:18 | v+python | create |
|