Use of third parameter in the WL.Client.InvokeProcedure

前端 未结 2 1286
离开以前
离开以前 2021-01-07 13:55

I am using the client side API WL.Client.InvokeProcedure(invocationData, options, UseSendInvoke) in worklight 6. But I could not find a description for the para

相关标签:
2条回答
  • 2021-01-07 14:20

    This parameter is used internally by WL authentication framework. Technically there should not be a reason for developer to use it.

    There are several ways to invoke adapters.

    (1) First one is via client application. This is where you use WL.Client.invokeProcedure(invocationData, options) API.

    (2) Second is by using adapter invocation service - http://pic.dhe.ibm.com/infocenter/wrklight/v6r0m0/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fdevref%2Fc_adapter_invocation_service.html. Basically issuing an http request to WL server and getting a response from adapter. RPC style.

    When you're doing it via (1) - you have two authentication layers - first is security test defined for application, second is security test defined for adapter procedure.

    When you're doing it via (2) - there is only one security layer - security test defined for adapter procedure.

    UseSendInvoke param (which is, once again, for internal usage) means that your application will go via path (2) instead of regular path (1).

    0 讨论(0)
  • 2021-01-07 14:20

    There's no UseSendInvoke argument that WL.Client.invokeProcedure takes, at least not in the public API defined in the documentation. You can look at the documentation for Worklight v6.0.0, Worklight v5.0.6, Worklight v5.0.5 to learn more about that particular API.

    0 讨论(0)
提交回复
热议问题