| Summary: | [api] getChangeSets Iterator | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Alvaro Sanchez-Leon <alvaro.sanchez-leon> |
| Component: | Mylyn | Assignee: | Alvaro Sanchez-Leon <alvaro.sanchez-leon> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | lmcbout, marco.masse, sebastien.dubois, steffen.pingel |
| Version: | 0.8 | ||
| Target Milestone: | 0.9 | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 330616, 355096 | ||
|
Description
Alvaro Sanchez-Leon
Update: Implementation started and is based on: 1) core api updates to return a ChangeSet Iterator 2) internal Blocking queue (core) to limit the number of parsed changesets e.g. max 40 3) implement thread to fill in queue as room becomes available e.g. looping to retrieve and resolve base and target versions in chunks of 20 changesets 4) modify UI to use the new interface and consume the elements in the queue via the iterator (In reply to comment #1) > Update: > Implementation started and is based on: > > 1) core api updates to return a ChangeSet Iterator > 2) internal Blocking queue (core) to limit the number of parsed changesets e.g. > max 40 > 3) implement thread to fill in queue as room becomes available e.g. looping to > retrieve and resolve base and target versions in chunks of 20 changesets > 4) modify UI to use the new interface and consume the elements in the queue via > the iterator The implementation above is specific to subclipse and therefore the implementation is now tracked on bug 355096 and Bug 355098 Implemented and committed |