| Hi Hugi,
Yes, this is a known problem with the WO api. You cannot patch it… like we have done with NSArray in the past to get generics support. “Patching” means making another .java class with the same package name and loading it before Apple’s…
In this case, patching won’t cure it because we need a “long” instead of an “integer” and there are several places where this API would have to change.
The simple answer is to live with the 2GB limit.
The longer answer… only by rewriting WO can you get around this, like TB is trying to do.
On May 8, 2014, at 5:15 AM, Hugi Thordarson < email@hidden> wrote: Thanks, but it’s not that. Apache handles large files just fine, so the problem seems to be with the WO adaptor.
Cheers, - hugi
Rebuild Apache with:
-DLARGEFILE_SOURCE -DFILE_OFFSET_BITS=64
And you'll be rollin'
Með kveðju,
Þór Sigurðsson
Tölvunarfræðingur - Forritari
Sími: 480-6000
<image001.png>
Samgöngustofa - www.samgongustofa.is
Umferðarstofa, Borgartúni 30, 105 Reykjavík
On 8.5.2014, at 08:49, Hugi Thordarson < email@hidden> wrote:
Hi all
I’m attempting to stream a ~3GB file from a WO app. When I DirectConnect to the app, the content-length header is correctly set to “3371573248”, but if the response goes through the Apache adaptor (CentOS 5.5/Apache 2.2), the content-length header is changed
to “2147483647” (Integer.MAX_VALUE), resulting in a truncated file for most clients.
I just attempted to install the most recent compiled Wonder adaptor from wocommunity org, but it doesn’t solve the problem.
Anyone familiar with this?
Cheers,
- hugi
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
Fyrirvari á tölvupósti / e-mail disclaimer
http://samgongustofa.is/fyrirvari/
|