Task #4306
Story #3755: Structural changes to D1 APIs for 2.0 release
Query API in MN and CN
100%
Description
The Query API in MN is it's own interface while the CN has the API in its Read interface. We should pick a location for both for consistency.
History
#1 Updated by Matthew Jones about 10 years ago
Maybe. The query API is optional in the MN, but required in the CN. So they could legitimately be in different places. Or not. But more importantly, we need to figure out how to mark optional service interfaces that MNs have a choice in implementing at any given Tier level. If they implement it, then it needs to pass tests, but if they don't implement it, then they should still pass at that Tier level.
#2 Updated by Ben Leinfelder almost 10 years ago
- Status changed from New to Closed
- translation missing: en.field_remaining_hours set to 0.0
MNQuery is not tied to any tier in our packaging structure. If it were in MNRead, then the implication would be that it is required for all tier 1 MNs, which it is not. Having it in MNQuery allows MNs to choose to implement that interface or not.
#3 Updated by Robert Waltz over 9 years ago
- Target version set to CCI-2.0.0
