IOperationServiceCallExternalOperation(Int32, String, String, Byte, ITerminal) Method |
Calls an operation which is implemented in another plugin.
Namespace: Resto.Front.ApiAssembly: Resto.Front.Api.V8 (in Resto.Front.Api.V8.dll)
Syntaxbyte[] CallExternalOperation(
int pluginModuleId,
string serviceName,
string operationName,
byte[] request,
ITerminal terminal = null
)
Parameters
- pluginModuleId Int32
-
Licensable module identifier of the plugin to be called. That module id have to be pre-shared with consumer plugins.
- serviceName String
-
Name of the external service which is implemented in another plugin. That name have to be pre-shared with consumer plugins.
- operationName String
-
Name of the external operation which is implemented in another plugin and have been registered using RegisterExternalOperation(String, String, FuncValueTupleByte, String, Int32, Guid, Byte). That name have to be pre-shared between producer and consumer plugins.
- request Byte
-
The data which will be transferred as an incoming argument into the external operation.
- terminal ITerminal (Optional)
-
Terminal for executing the external operation remotely. Leave it null to execute the operation on the local terminal.
Return Value
Byte
Response returned by the producer plugin.
Exceptions
Remarks
Different plugins running under the same Syrve POS application instance can communicate via external operations. Syrve POS just transfers requests and responses between plugins without knowing any details. Both producer and consumer plugins should understand the data structure, developers should negotiate a protocol specification, pre-share operation names, handle versioning and so on. Producer plugin registers an operation using
RegisterExternalOperation(String, String, FuncValueTupleByte, String, Int32, Guid, Byte) and consumer plugin call it using
CallExternalOperation(Int32, String, String, Byte, ITerminal).
See Also