Bug 1092880

Summary:	[Docs] [Technical] [async]max parameter needs better explanation and usage example
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Andrew Burden <aburden>
Component:	Documentation	Assignee:	Andrew Burden <aburden>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ruediger Landmann <rlandman>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	3.4.0	CC:	gklein, juwu, luvilla, rbalakri, yeylon
Target Milestone:	---
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-16 04:47:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.