[Isomorphic]

saveData() ultimately goes through the DataSource, so saveData() does whatever the DataSource is configured to do, which can be anything.

We're assuming that you're using a DataSource loaded from a .ds.xml file, so that's dataProtocol:"iscServer". As we've covered a couple of times, your custom servlet won't be parsing the special iscServer-format request, so it won't be able to send a normal response. Hence the showPrompt:false/timeout hack we suggested.

So now you're going down the iframe route, seemingly just to avoid a harmless hung request in the RPC Tab.. we'd suggest taking a step back. Are you chasing a real problem at all?

In the first place, unless you really do plan to have thousands of people simultaneously uploading large files, setting a large heap size makes it vanishingly unlikely that there would ever actually be an issue with running out of memory.

Remember that even for people whose connection is slow enough that uploading takes some time, each user is only taking up memory for the part of the file that has been uploaded so far, not the whole file.

Beyond that, why would you delve deeply into iframes and direct JavaScript use just to get rid of a hung request? Aren't there real bugs or features needing implementing? :)

[sderouchie]

The iFrame route is because the overview documentation provided is what made that suggestion.

If you're suggesting that the hack route is better, then I will go that way. I was avoiding it because given the options "a hack v.s. the most correct way", I would assume the most correct way would be the way to go :)

Unfortunately, yes, I am chasing a real problem. The issue I have been tasked with fixing is the case where an 850M file is uploaded. A single person uploading an 850M file causes it to run out of memory.

We have to support 32-bit JVMs, and I have the memory set as high as it can go (just under 1.5G)-- any higher and the JVM won't start.

With the servlet you provided earlier, I've been able to test a 3G file that uploaded without issue other than this hang. I will try this hack.

Thanks.

[Isomorphic]

While the iframe route is the most correct way, it's rather advanced, so we would advise you to either just use the hack or solve the problem via Feature Sponsorship instead.