Ticket #339 (closed todo: done)
link between QueryFocus and session
| Reported by: | ichthyo | Owned by: | ichthyo |
|---|---|---|---|
| Priority: | normal | Milestone: | 0integration |
| Component: | lumieraProc | Keywords: | session lifecycle |
| Cc: | Blocked By: | #310, #400 | |
| Blocking: | #204, #639, #676 |
Description (last modified by ichthyo) (diff)
work out how the QueryFocus can use the session / placement index for discovering scope contents. Especially make sure this works in conjunction with the session lifecycle.
Change History
comment:1 Changed 2 years ago by ichthyo
- Status changed from new to accepted
- Description modified (diff)
- Blocked By 400 added; 319 removed
- Summary changed from session attaching to QueryFocus to link between QueryFocus and session
comment:2 Changed 23 months ago by ichthyo
Question: how does the other direction work, i.e. the session updating the "current" QueryFocus?
comment:5 Changed 16 months ago by ichthyo
So basically this is reduced now to accessing the session through the SessionServices API, which is intended for internal use by Proc-Layer code. Any access here calles through the session manager pImpl, allowing to switch the current session in a quasi transactional way.
The mentioned "reverse direction" of this relation is intended to be handled by the QueryFocus following the actual access operations on the model in a semi-automatic fashion (see #676)
comment:6 Changed 16 months ago by ichthyo
- Status changed from accepted to closed
- Resolution set to done
So basically model and session core (PlacementIndex) are tightly integrated now, without directly coupling the implementations.
as a sideeffect of working out the QueryResolver API, this got almost completely solved. Indeed the meaning is changed, as now there isn't any active "registration" necessary anymore.