Downloading large files works fine, for uploads there are several bugs
in the WO code. I reported it via the Apple bug reporter some time ago.
Problem ID: 10765546
There is no workaround, here is some input in case somebody from Apple
is looking into it:
The class com.webobjects.appserver._private.WOHttpIO tries to parse the
content-length header with the method parseInt of the Integer class.
This will fail for all files larger than 2.1GB. Further there are many
instances in the code that make use of an integer for the content length
of a request:
WOInputStreamData: public WOInputStreamData(InputStream, int)
WORequest: public int _contentLengthHeader()
Also classes not directly involved in the request handling do show such
a limitation (e.g. public NSRange(int, int)).
PS: looking forward to see many of you at WOWODC 2012 in Montreal
Regards
Helmut Tschemernjak
On 13.06.12 09:45, Johann Werner wrote:
Just hitting the same problem for uploading files > 5GB. Does anyone has
already done some work relating to that problem?
Am 05.03.2012 um 00:51 schrieb Q:
On 05/03/2012, at 9:40 AM, Lachlan Deck wrote:
Hey Alan,
On 05/03/2012, at 9:32 AM, Alan Ward wrote:
Speaking for myself (and definitely not on behalf of my employer) I'm curious
where you are coming from here? Did you have a contract that obligated Apple
to continue to support you? What grounds to you believe you have for a law
suit? I'm just curious.
Yes it's a somewhat comical notion :-)
Just to make your point/question clearer for people: the said product was
supplied for free for the last few releases. So if people were to sue for
damages, it would need to be a very strong case indeed! I'm sure Apple would be
happy to supply a full refund ;-)
More seriously, I think the sentiment is coming from promises (or assumed
promises) that were made when, for example, the Xcode tools were dropped. The
reasoning given was to concentrate on enhancing the frameworks. Thus the
initial impression given to the community by Apple (bolstered by its funding of
tools like WOLips) was that a renewed energy was being put into WO by Apple
that people could continue to build their business apps with. And, there was
some initial promise of better community involvement in the evolution of WO
when the Apple maven repo was made available (which showed some future versions
in the works). It didn't last long though which was a shame at the time,
especially for us maven users. Hmm so, perhaps it was the community's
unwillingness to embrace maven that canned it moving forward :-)
What are you trying to say? Maven killed WebObjects? Why am I not surprised. :)
cheers,
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/helmut%40helios.de
This email sent to hel...@helios.de
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
