Dev Estimate: 3
Test Estimate: 0
Like most services, the Service Bus will return a partial list, with a continuation to get more, if you use TOP or if the number of results crosses some threshold. For example, with a call like this, when the server has more than 22 queues:
https://XXX.servicebus.windows.net/$Resources/Queues?%24top=2&%24skip=20
the server can return:
<feed xmlns="http://www.w3.org/2005/Atom">
...
<link rel="self" href="https://azuresdkdev.servicebus.windows.net/
$Resources/Queues?%24top=2&%24skip=20"/>
<link rel="next" href="https://azuresdkdev.servicebus.windows.net/
$Resources/Queues?%24top=2&%24skip=22"/>
However, that "next" link is not returned to the consumer of the API. This means that the List_Result classes need to parse and *expose_ those continuations to the user, so they can use them to get the next batch of results. For example, this is what is done with the Blob APIS, ListBlobsResult has a Marker and a NextMarker properties.
(The PHP SDK has a similar issue, tracked Azure/azure-sdk-for-php#479)
Dev Estimate: 3
Test Estimate: 0
Like most services, the Service Bus will return a partial list, with a continuation to get more, if you use TOP or if the number of results crosses some threshold. For example, with a call like this, when the server has more than 22 queues:
the server can return:
However, that "next" link is not returned to the consumer of the API. This means that the List_Result classes need to parse and *expose_ those continuations to the user, so they can use them to get the next batch of results. For example, this is what is done with the Blob APIS,
ListBlobsResulthas aMarkerand aNextMarkerproperties.(The PHP SDK has a similar issue, tracked Azure/azure-sdk-for-php#479)