Blocking/non-blocking http requests

Pierre Sahores sc at
Wed Oct 16 13:43:09 EDT 2013


While "PUT" commands can be unauthorized for good security reasons, i never had to do with a server configured to reject  "POST" commands whose are, by the way, always more easy to manage securely than the "GET" ones. 

Yes, we can depend from the server's response against HTTP POST and GET commands in checking the "it" variable before going head with the next line of script execution, even if the HTTP message comes from a client side AJAX asynchronous request (the asynchronous mode impacts only the client side way to submit and handle the server's response; it do not impact at all the server-side way to receive and reply to it).

Last but not least, long time ago (before 2003), the Metacard engine went buggy handling the POST command 1 period peer sequence of 20 consecutive POST requests he received. This bug disappeared definitively with, at least, Rev 2.0.3 and upon (the first version of Rev i used for my own).

The GET command is available on all platforms, LC-Server included while the POST command is available on any platforms except LC-Server witch can only accept and reply to the ones he receive from client-side apps.

AFAIK, Monte's external suites extends this basics in useful ways on the iOS and Android platforms.

Le 16 oct. 2013 à 19:04, J. Landman Gay a écrit :

> Some url methods block (PUT, POST) and some don't (GET). As far as our scripts are concerned, can we always depend on the request completing before the next line of script executes?
> -- 
> Jacqueline Landman Gay         |     jacque at
> HyperActive Software           |
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

Pierre Sahores
mobile : 06 03 95 77 70

More information about the Use-livecode mailing list