Skip to content

Spike: Service Bus: List*Result classes need to surface continuations #94

Description

@jcookems

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&amp;%24skip=20"/>
  <link rel="next" href="https://azuresdkdev.servicebus.windows.net/
    $Resources/Queues?%24top=2&amp;%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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions