Rpc callAsync Api

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Rpc callAsync Api

halcwb
In the api it's not clear that successive arguments after the callback and method arguments will be passed on as params, for examples:

(function callRpcServer ()
{
  var rpc = new genpres.overrides.io.remote.Rpc();
  rpc.setTimeout(10000);
  rpc.setUrl("../../../DirectRouter/Index");
  rpc.setServiceName("Patients");

  // call a remote procedure -- takes no arguments, returns a string
  var that = this;
  this.RpcRunning = rpc.callAsync(
    function(result, ex, id)
    {
      that.RpcRunning = null;
      if (ex == null) {
        console.log(result);
      } else {
        alert("Async(" + id + ") exception: " + ex);
      }
    },
    "GetPatientDetails", "123456");
})()

Will result in the number "123456" being added to the params array.
Reply | Threaded
Open this post in threaded view
|

Re: Rpc callAsync Api

fritz
http://demo.qooxdoo.org/current/apiviewer/#qx.io.remote.Rpc~callAsync!method_public

says:

     callAsync(Function handler, String methodName)

     Makes an asynchronous server call. The method arguments (if any) follow
     after the method name (as normal JavaScript arguments, separated by
     commas, not as an array).

At least it's described in the documentation.

Cheers,
Fritz

On Wed, 24 Dec 2014, halcwb wrote:

> In the api it's not clear that successive arguments after the callback and
> method arguments will be passed on as params, for examples:
>
> (function callRpcServer ()
> {
>  var rpc = new genpres.overrides.io.remote.Rpc();
>  rpc.setTimeout(10000);
>  rpc.setUrl("../../../DirectRouter/Index");
>  rpc.setServiceName("Patients");
>
>  // call a remote procedure -- takes no arguments, returns a string
>  var that = this;
>  this.RpcRunning = rpc.callAsync(
>    function(result, ex, id)
>    {
>      that.RpcRunning = null;
>      if (ex == null) {
>        console.log(result);
>      } else {
>        alert("Async(" + id + ") exception: " + ex);
>      }
>    },
>    "GetPatientDetails", "123456");
> })()
>
> Will result in the number "123456" being added to the params array.
>
>
>
> --
> View this message in context: http://qooxdoo.678.n2.nabble.com/Rpc-callAsync-Api-tp7586517.html
> Sent from the qooxdoo mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>

--
Oetiker+Partner AG              tel: +41 62 775 9903 (direct)
Fritz Zaucker                        +41 62 775 9900 (switch board)
Aarweg 15                            +41 79 675 0630 (mobile)
CH-4600 Olten                   fax: +41 62 775 9905
Schweiz                         web: www.oetiker.ch

------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Rpc callAsync Api

halcwb
You're right. Overlooked it.