diff options
| -rw-r--r-- | scripts/PLAN | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/scripts/PLAN b/scripts/PLAN index 6e61759b..fc61268f 100644 --- a/scripts/PLAN +++ b/scripts/PLAN @@ -69,3 +69,35 @@ SQL: - SQL to UPDATE ... - SQL to DROP ... + + + +At this point it's starting to look like the pdu objects in +rpki.left_right are a subclass of a more general class of objects that +live in SQL (duh, again). This makes sense as left-right protocol was +designed to let us frob a subset of the rpki database on the wire. + +Need to check whether current rpki.left_right objects map cleanly to +data structures we're saving in SQL. They should, but check anyway. + +Hmm, it's more complicated than that. Most of left_right maps well, +but portions (eg, <list_resources/>) are just commands and do not. +Mixin? We have a varient of this same problem with the mixins I'm +already using in irbe-cli.py. + +Also need to think about up-down protocol, currently separate but some +of these objects might map there too. This is why I originally +intended to code all of these as separate object hierarchies even +though in some cases they look awfully similar. Hmm, implement as +separate hierarchies with sideways conversion methods? Still feels +wrong, but so does turning this into one big interconnected mess. + +Ok, up-down XML is all structured as commands, data is all attributes +and (occasionally) element content, so not very close match to db. + +So this appears to break out fairly cleanly: objects shown in blue in +the repository-engine-objects.pdf picture are both left-right PDU +objects and database objects, objects shown in green are only database +objects, and left-right PDU objects not shown in that picture are just +left-right PDUs. Or something close to this, details need checking. +So this does look like some kind of mixin would be appropriate. |