Currently, POST requests to the /SASjsApi/stp/execute will always return a JSON object. This has the benefit of being easy to parse by client apps, however it also has a serious performance impact for larger payloads, eg:
The processing time needed to serialise the webout / log JSON on the server side
The increase in the payload size, eg when including the LOG file (JSON wrapper)
To illustrate - the request below took 2.5 minutes to generate, then 18 seconds to download (16mb):
The Proposal:
Send back the raw value of webout.txt directly in the response
Append the log if DEBUG >0 or if the SAS executable returned a non-0 response
Use a separator to distinguish the two in the response (to be determined)
This will require corresponding updates in the Adapter and other SASjs-linked applications.
Currently, POST requests to the
/SASjsApi/stp/execute
will always return a JSON object. This has the benefit of being easy to parse by client apps, however it also has a serious performance impact for larger payloads, eg:To illustrate - the request below took 2.5 minutes to generate, then 18 seconds to download (16mb):
The Proposal:
This will require corresponding updates in the Adapter and other SASjs-linked applications.