A number of constraints apply when you use this pattern.
You can use the
Worklight: resource handler
pattern only if you meet all of the following constraints:
-
Mobile applications must send their requests to Worklight via the
WL.Client.invokeProcedure
API.
-
Mobile applications must support a synchronous request response interaction
style.
-
Procedure handler subflows, and therefore any backend systems that they interact
with, must be able to respond to requests in a time frame appropriate for
synchronous interaction.
-
If logging or error handling is required, the format used by this pattern is
assumed to meet your requirements.
-
A consistent model for representing the resource as a JSON object must be used
for both the Message Broker procedure handler subflows and the mobile application.
-
Each instance of the resource can be identified by a unique identifier.