As I stated earlier, this problem was fixed in 4D 2003 at Brendan Coveney's behest.
Except that's not the problem I'm referring to. The problem is that 4D web's server buffers the whole request into memory. In my particular application, the PUT data could be more than I care to store in memory at once. The problem is that I need to flush the data out to a file before the PUT is complete, not just reject the PUT if it gets too big.
If that problem has been fixed in 2003, let me know. -- Christophe, Fish Head, Blowfish <[EMAIL PROTECTED]>
