I think all RPCs are done via POST, and any data that don't fit in the
URI (according to something of a guess about URI size limits) are
automatically put into the POST data. Do you have a concrete use case
that shows a problem in any real browser?
On 11/12/2013 09:03 PM, Chris Double wrote:
I'm using a JavaScript API that requires calling back to my UrWeb app
passing it a large string of authentication data. I'm using 'rpc' to do
this. It looks something like:
fun dosignin (assertion:string) = ...
(* This is called on page load in JavaScript. 'watch' is a JS
function that takes a callback argument. At some point the JS
library calls this function which does the callback to the server
pasing it a long 'assertion' string
*)
fun onload () = watch (fn x => rpc (dosignin x)) None
This works but results in an enormously large URL when calling
'dosignin'. Is it possible to have this done via POST to work around
possible browser URL length issues?
_______________________________________________
Ur mailing list
[email protected]
http://www.impredicative.com/cgi-bin/mailman/listinfo/ur
