On Aug 13, 2007, at 6:16 AM, Aaron Freeman wrote:
> I see from your link that Sun uses an int, but couldn't that be
> I don't believe Jakarta, and other implementations have this limit
> -- I just
> looked and they are using a long. This is a seriously limiting
> factor and
> may require us to swap out our underlying servers from Resin (which I
> really, really don't want to do).
The HttpServletRequest.getContentLength() will still return int, but
Resin will be able to use a long value internally (in 3.1.3).
However, you could also use chunked-encoding for your uploads
(assuming you have control over your client). That would avoid the 32-
bit issue entirely.
> Aaron Freeman
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Serge
>> Sent: Friday, August 10, 2007 10:16 AM
>> To: General Discussion for the Resin application server
>> Subject: Re: [Resin-interest] Content-Length
>> Aaron Freeman wrote:
>>> Looking at com.caucho.server.connection.AbstractHttpRequest and
>>> com.caucho.server.http.HttpRequest I see that contentLength
>> is being
>>> defined as an "int", which limits file uploads to a size of
>>> How painful would it be to convert this limit to a "long"
>> so that we
>>> can have substantially larger files?
>> That's a servlet API limitation, not something resin can do
>> without breaking their support for the spec really:
>> Serge Knystautas
>> Lokitech >> software . strategy . design >>
>> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
>> resin-interest mailing list
> resin-interest mailing list
resin-interest mailing list