Task #6871 (new)
Opened 8 years ago
Last modified 3 years ago
RFE: all top-level BlitzGateway fetchers should take offset/limit
| Reported by: | jamoore | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | API | Version: | n.a. |
| Keywords: | n.a. | Cc: | python-team@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
In order to begin handling large amounts of data, all the BlitzGateway? methods which could return unlimited sets like listProjects, should also take an offset and limit value.
Perhaps if limit=-1 or similar, then a generator is returned which will step through the data, but in general we should encourage API consumers to be aware of the fact that a LOT of data could be returned by one of these methods.
Change History (5)
comment:1 Changed 7 years ago by wmoore
- Milestone changed from OMERO-Beta4.4 to OMERO-Beta4.4.1
comment:2 Changed 7 years ago by jmoore
comment:3 Changed 3 years ago by jamoore
Referencing ticket #9092 has changed sprint.
comment:4 Changed 3 years ago by jamoore
Referencing ticket #9092 has changed sprint.
comment:5 Changed 3 years ago by jamoore
- Milestone changed from 5.x to Unscheduled
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Referencing ticket #9092 has changed sprint.