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? :)
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? :)
Comment