Opened 8 years ago

Closed 6 years ago

#1382 closed enhancement (wontfix)

datasource interface for signaling capabilities

Reported by: jelte Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: data source Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

We do not expect every data source implementation to support every type of action; some will be 'read-only', and hence will not support things like updating etc. We can (and do) already throw NotImplemented? exceptions if these functions are called, but we should really not call them in the first place if the implementation is not able to do it anyway.

So the proposal is to add a method that returns what the datasource can and cannot do (iteration, updating, journaling, perhaps more) so any callers can more cleanly handle cases where these are not supported.

Subtickets

Change History (4)

comment:1 Changed 8 years ago by jelte

  • Summary changed from datasrouce interface for signaling capabilities to datasource interface for signaling capabilities

comment:2 Changed 8 years ago by shane

  • Milestone changed from New Tasks to Year 3 Task Backlog

comment:3 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:4 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check http://bundy-dns.de.

Closing ticket.

Note: See TracTickets for help on using tickets.