Design client library #1135

Activity

1. lukpueh

   added this to the Client Refactor milestone on Sep 10, 2020
2. joshuagl

   added

   clientRelated to the client (updater) implementationRelated to the client (updater) implementation

   on Sep 10, 2020
3. lukpueh

   added

   discussionDiscussions related to the design, implementation and operation of the projectDiscussions related to the design, implementation and operation of the project

   on Sep 10, 2020
4. joshuagl commented on Sep 10, 2020

   

   joshuagl

   on Sep 10, 2020

   Last edited by joshuagl

   Member

   More actions

   Things to consider, based on learnings from a PoC integration with pip (cc @jku):

   • download progress reporting Updater: No download progress hooks #1057 handled with the abstract Fetcher interface Abstract out the network IO #1250
   • allowing a package manager to plug-in their own network/download stack resolved with the abstract Fetcher interface Abstract out the network IO #1250
   • minimal footprint (minimal dependencies and being able to be installed independently of the repository library and tools)
   • supporting metadata and targets on separate hosts, and different targets on different hosts client/updater design: mirror config redesign #1143
   • ability to check for existence of local configuration for a given repository Updater: Add ability to check for existence of (local) repository #1063

   TAPs to be aware of when designing:

   • TAP 3: Multi-role delegations – accepted, but not in the specification because it is not implemented for the reference implementation
   • TAP 4: Multiple repository consensus on entrusted targets – accepted, but not yet in the specification. Implemented in the current reference implementation
5. jku commented on Sep 14, 2020

   

   jku

   on Sep 14, 2020

   Last edited by jku

   Member

   More actions

   • allowing a package manager to plug-in their own network/download stack

   Filed #1142 for this

   👍React with 👍1Reacted by Joshua Lock
6. jku commented on Sep 14, 2020

   

   jku

   on Sep 14, 2020

   Member

   More actions

   • supporting metadata and targets on separate hosts, and different targets on different hosts

   and #1143 for this

   👍React with 👍1Reacted by Joshua Lock
7. jku commented on Oct 2, 2020

   

   jku

   on Oct 2, 2020

   Member

   More actions

   See #1158 for "client/updater: Parallel Downloads"

   ❤️React with ❤️1Reacted by Lukas Pühringer
8. joshuagl

   added

   decision recordOutcome of this discussion should be tracked in a decision recordOutcome of this discussion should be tracked in a decision record

   on Oct 14, 2020
9. joshuagl commented on Oct 14, 2020

   

   joshuagl

   on Oct 14, 2020

   Member

   More actions

   We're seeing multiple areas where the current Updater interface/API is brittle or confusing (#1143, #1174, possibly others).

   I had originally expected that we would try to maintain the current updater API, but we should review that and even if we do stay close to the current API plan to fix the confusing/outdated/inflexible aspects.
10. jku commented on May 19, 2021

    

    jku

    on May 19, 2021

    Member

    More actions

    I had originally expected that we would try to maintain the current updater API, but we should review that and even if we do stay close to the current API plan to fix the confusing/outdated/inflexible aspects.

    Same same.

    Now that we've kicked out mirrors (so are not directly compatible anyway) and now that I've had time to think about it, I think we should improve the API as much as we can. It'll still be quite close to the old one (so not hard to port) but hopefully an improvement.

    Latest ideas in #1317 (comment)
11. sechkova

    added

    backlogIssues to address with priority for current development goalsIssues to address with priority for current development goals

    on May 26, 2021
12. joshuagl

    removed

    backlogIssues to address with priority for current development goalsIssues to address with priority for current development goals

    on Jul 28, 2021
13. MVrachev commented on Aug 27, 2021

    

    MVrachev

    on Aug 27, 2021

    Last edited by MVrachev

    Collaborator

    More actions

    I think that in a way this issue and issue #1317 are covering the same stuff.
    Do we need that one?
    If we don't, I think the only two proposals left that are not addressed are

    TAPs to be aware of when designing:

    • TAP 3: Multi-role delegations – accepted, but not in the specification because it is not implemented for the reference implementation
    • TAP 4: Multiple repository consensus on entrusted targets – accepted, but not yet in the specification. Implemented in the current reference implementation

    which we can move in #1317 as TODO items.
14. jku commented on Sep 17, 2021

    

    jku

    on Sep 17, 2021

    Member

    More actions

    IMO the final missing piece(s) here might be documented in #1580.
15. jku commented on Nov 30, 2021

    

    jku

    on Nov 30, 2021

    Member

    More actions

    I'm sure there are features that are still wanted by someone, but I think the client design is now done and implemented: anything still missing is a new feature, closing this one
16. jku

    closed this as completedon Nov 30, 2021