DWR

Андрей Чепцов <andrey.cheptsov@gmail.com>:

I faced with the problem while I was using cross-domain DWR script-on-demand mode (ScriptTag). The fact is that in IE in other browsers there is the restriction on maximum url's length for GET request. This leads to the situation when I am trying to send large data (that is encoded into the url) and url contains more than 2083 characters (IE support this maximum length) it doesn't retrieve response. This is critical problem in my project because I need send data anyway and send them cross-domain.
 
I know there was solution of such problem by fragmentation of requests, i means send long request by parts and than put it in one and process. Do DWR team have plans to implement the solution or not, or at least how to manage with this issue using DWR, can someone answer?

it is not possible to fragment the requests at ana application level because I just use DRW's to call Java's methods on my server side and I call for instance this javascript code: myVar.myJavaMethod(objectToSave, function() { ... }); And the thing is objectToSave after serialization more than 2083 characters (in common case because for example I fill form where fields could be rather long, all this is contained by mu objectToSave that I need to send to server). It would be quite reasonable to support sending of requests with large data (and it is not so much, just kore than 1 kb) by injection in engine.js where it could divide url into parts and make several <script> tahs instead of one, and than it need to be changed the servlet a little to wait all parts of requests and only after that process the request.