Ok thanks for the link Jim.
Essentially what 4D is saying (and it makes sense) is that the BLOB will
need a contiguous block of memory and so if memory is fragmented and no
block large enough exists 4D rejects the entire upload. That may be why I
was getting inconsistent limits on different days.
I've been dealing with the same thing. Uploading a zipped, built
application to a "pub" server.
I'd get different results testing on different machines. It's said in this
thread, that ultimately the file is in a blob, and a blob needs contiguous
blocks of memory. The state of memory could vary.
I seem to remember in the past there was a way to get the entire body and one
would have to parse the contents in order to delineate the part that was the
uploaded file.
Also if you do a WEB GET VARIABLES you will get an out of memory error if
the file is too large (413 - Request Entity Too Large)
The thing with file upload seems to be a bit strange ...
I did some tests and upload a file with size 888.3 MB, no problem.
Another test with a larger file with size 4.4G didn't work. Only a chunk of
334.9 MB (to be exact: 351255546 bytes) was handled. I'm not able to explain
this behavior.
Reg
4 matches
Mail list logo
