SF Project Link
Here is the list of URL querystring parameters that will be on the URL to support communicating when the script has finished loading, and to support multipart requests. Underscores are used on the parameter names to help avoid conflict with the application/web site's parameters.
A unique ID to identify the full request, if it is a multipart request. Sent with every multipart request. ID may only be unique to within a web page instance. The server should be careful about multiple open pages and/or users sending the same ID.
The current part number, if it is a multipart request.
Building on the first example, say there is a third parameter bar=ThisIsAReallyLongValue (where that value *is* very long, over the 1 KB limit). The set of script URLs would be:
http://somedomain.com/serverpath?_id=id1&_part=1_partOk=partComplete&_error=requestError&target=foo&color=blue&bar=ThisIsAReIn addition to the requestComplete and requestError functions described in the first example, the page would also have this method defined:
The Multipart URL example showed that some of the URL parameters might get segmented across requests, and it might get segmented
in the middle of the value of a name=value pair. If that is the case, the next request will contain the next segment of the value, with the name= in front of it.
So, for the above example:
was segmented like this:
Any of the "constant parameters" that the server needs will never be segmented.
Tagneto support this API via the Dsr.send() method defined in Dsr.js. send will add all of the above parameters, and will segment the URL into a multipart URL if it is bigger than 1KB.
Outstanding implementation issues:
2005-11-22: Initial version.