Access return header invokeHttp

[marc.kusters]

For a REST web service I want to consume I want to use pagination. However, for this specific web service this data is provided with by the return header. Is there someway to access this information using invokeHttp? Otherwise I need to bruteforce it by increasing the header page count and checking if the count of the results is larger then 0.

As far as I know and can see the only return values is the result column.

[rareddy]

Looks like they are captured but not exposed through the invokeHttp. It may need an enhancement to make it happen

[marc.kusters]

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.

[rareddy]

Yes, you can do that by having two or more procedures at view model and join

[shawkins]

> 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.