Bug 1092880 - [Docs] [Technical] [async]max parameter needs better explanation and usage example
Summary: [Docs] [Technical] [async]max parameter needs better explanation and usage ex...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 3.5.0
Assignee: Andrew Burden
QA Contact: Ruediger Landmann
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-30 07:44 UTC by Andrew Burden
Modified: 2015-02-16 04:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-16 04:47:01 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Andrew Burden 2014-04-30 07:44:47 UTC 
Luca Villa wrote:
the use of the max= parameter to influence the number of results when the default number of 100 is insufficient should be also mentioned/duplicated on the pagination section as they seem to be strictly related.
A usage example would be even better.
Note You need to log in before you can comment on or make changes to this bug.