Yeah this wasn't fully fixed until later ... I think maybe 5.4.3
changed the response streaming api's to take longs, but didn't
fix wohttpio and worequest to make them parse content length as
long.
Perhaps, assuming you're still on the inside, you'd be able to
slip 5.4.3.1 (or whatever it got up it internally) under the door
somewhere (?)
:)
Asking that on a public mailing list hosted by Apple is not a
great idea :-)
Don't worry ... The public and private answer is the same :)
And the answer will probably be: "the community should fix it in
Wonder" :-)
This would be great but I fear outside my scope. I've developed a wo
app to manage video/audio content at the university and the uptake has
been great. It's hard enough justifying WebObjects here, and issues
such as this, if it cannot be resolved, raise more eyebrows.
Gordon
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/gordon.belray%40utoronto.ca
This email sent to [email protected]
Gordon Belray
Systems and Interface Designer
Information Technology Services
University of Toronto Libraries
[email protected]
416-946-8617 w
416-427-7007 m
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
