-
1. Re: Access return header invokeHttp
rareddy Sep 23, 2019 10:37 AM (in response to marc.kusters)Looks like they are captured but not exposed through the invokeHttp. It may need an enhancement to make it happen
-
2. Re: Access return header invokeHttp
marc.kusters Sep 23, 2019 11:52 AM (in response to rareddy)Oh, thats too bad if the information is already there.
I solved it with a bit of bruteforce doing a count and increasing the page number manually.
Is there a way to make two REST calls concurent? The situation is as follows; We have to do 2 calls to the REST API to get all the data we need due to multiple nested elements. Since the API calls take most of the time, is it possible to do those concurrent so that we can join the two resulting tables without having to wait a long time before the other procedure is done.
If this is possible I think the best place to do the concurrent calls would be in the view that joins both procedures.
-
3. Re: Access return header invokeHttp
rareddy Sep 24, 2019 9:35 AM (in response to marc.kusters)Yes, you can do that by having two or more procedures at view model and join
-
4. Re: Access return header invokeHttp
shawkins Sep 24, 2019 3:37 PM (in response to rareddy)> Yes, you can do that by having two or more procedures at view model and join
It will depend on the query structure - having each execution in a union branch will make them parallel, as will a simple nested loop join. But if there is one is a nested table to the other or a dependent join is planned, then they will be executed serially.