Opened at 2009-10-09T14:34:03Z
Closed at 2010-10-18T00:46:01Z
#303 closed todo (done)
Interface to Placement index
| Reported by: | Ichthyostega | Owned by: | Ichthyostega |
|---|---|---|---|
| Priority: | normal | Milestone: | 0integration |
| Component: | lumieraSteam | Keywords: | interfaces design |
| Sub Tickets: | #79, #302, #352, #372, #407 | Parent Tickets: | #115, #304, #440 |
Description (last modified by )
Shape the PlacementIndex interface, decide how to expose it to clients and document it.
Change history (13)
comment:1 by , at 2009-10-09T14:37:55Z
| blocking: | 79 → 79, 304 |
|---|
comment:2 by , at 2009-10-16T19:43:11Z
| blockedby: | 302 → 302, 340 |
|---|
comment:3 by , at 2009-10-16T21:19:43Z
| Status: | new → accepted |
|---|
comment:4 by , at 2009-10-17T15:44:27Z
| blockedby: | 302, 340 → 302, 340, 352 |
|---|
comment:5 by , at 2009-10-20T00:43:22Z
| blockedby: | 302, 340, 352 → 302, 340, 352, 372 |
|---|
comment:6 by , at 2009-11-06T18:59:14Z
| blocking: | 79, 304 → 79, 115, 304 |
|---|
(In #115) there is an interconnection to the query facilities on PlacementIndex: what form of "placement" (language ref, PlacementRef, equivalent Placement instance) is acceptable when invoking query operations?
comment:7 by , at 2009-11-12T01:07:30Z
| blockedby: | 302, 340, 352, 372 → 302, 340, 352, 372, 407 |
|---|
comment:8 by , at 2009-12-28T02:43:39Z
| blockedby: | 302, 340, 352, 372, 407 → 302, 352, 372, 407 |
|---|
(In #340) This task has been shifted over from the PlacementIndex to ContentsQuery, while the index is now a rather low-level implementation facility. As far as I can see, the more generic query operations are coded up; but there should be a conclusive list what will be required by the public session API
comment:10 by , at 2010-01-16T10:05:21Z
| blockedby: | 302, 352, 372, 407 → 79, 302, 352, 372, 407, 440 |
|---|---|
| blocking: | 79, 115, 304 → 115, 304 |
| Keywords: | session removed |
| Priority: | grave → normal |
what remains here is mostly checking the sanity of the design done thus far
comment:11 by , at 2010-10-18T00:43:47Z
| blockedby: | 79, 302, 352, 372, 407, 440 → 79, 302, 352, 372, 407 |
|---|---|
| blocking: | 115, 304 → 115, 304, 440 |
comment:12 by , at 2010-10-18T00:46:01Z
| Description: | modified (diff) |
|---|---|
| Resolution: | → done |
| Status: | accepted → closed |
closing that now...
This topic is somewhat strange. PlacementIndex started out as an important API and mutated into a core facility within the session, but almost completely shielded from client code by now. Anyway, the PlacementIndex interface survived some months and implementation of several facilities built on top by now, without significan change, and thus can be considered final.
comment:13 by , at 2025-12-25T00:00:00Z
| blockedby: | 79, 302, 352, 372, 407 |
|---|---|
| blocking: | 115, 304, 440 |
| Parent Tickets: | → 115, 304, 440 |
| Sub Tickets: | → 79, 302, 352, 372, 407 |
Migration MasterTickets ⟼ Subtickets-plugin
now working on the Placement-Scope topic