Ticket #319 (accepted todo)

Opened 10 months ago

Last modified 4 months ago

define generic and specific query API

Reported by: ichthyo Owned by: ichthyo
Priority: urgent Milestone: 0integration
Component: lumieraProc Keywords: interfaces design session
Cc: Blocking: #306, #318, #340, #412
Blocked By: #182, #500, #539, #639

Description (last modified by ichthyo) (diff)

  • decide what kind of operations goes on which part of the API
  • care for adding them to the relevant classes consistently

Change History

Changed 10 months ago by ichthyo

  • blocking 318 added

Changed 10 months ago by ichthyo

  • blocking 339 added

Changed 10 months ago by ichthyo

  • blocking 340 added

Changed 8 months ago by ichthyo

  • blocking 339 removed

(In #339) 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.

Changed 7 months ago by ichthyo

  • blocking 412 added

(In #412) 90% of the implementation is in place now, so this boils down to defining a sensible API

Changed 7 months ago by ichthyo

  • keywords session added; sesion removed

Changed 7 months ago by ichthyo

  • blockedby 500 added

Changed 5 months ago by ichthyo

  • blockedby 539 added

Changed 5 months ago by ichthyo

  • blocking 546 added

Changed 4 months ago by ichthyo

  • status changed from new to accepted
  • blocking 546 removed
  • description modified (diff)

Considering the basic spec as done now. Still have to code up all the individual API functions

Changed 7 weeks ago by ichthyo

  • blockedby 639 added
Note: See TracTickets for help on using tickets.