[
https://issues.apache.org/jira/browse/MRESOLVER-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941876#comment-17941876
]
ASF GitHub Bot commented on MRESOLVER-685:
------------------------------------------
cstamas merged PR #679:
URL: https://github.com/apache/maven-resolver/pull/679
> Connector pipelining
> --------------------
>
> Key: MRESOLVER-685
> URL: https://issues.apache.org/jira/browse/MRESOLVER-685
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.8
>
>
> We need to come up with some solution to "order/pipeline" connectors.
> Currently existing connectors in Resolver are:
> * basic -- handles transport and checksum validation; the only connector
> existing in system so far
> * RRF -- wraps another connector and applies remote repository filter rules;
> if enabled, wraps basic as rrf( basic() )
> Not yet in resolver connector:
> * mimir -- this should be moved into Resolver ("caching-connector"), this
> connector offers global cache (per workstation) and more (LAN wide caches)
> To be done connector:
> * signature -- connector that validates signatures
> Pipelining (or at least wrapping ordering) would be handy, as we want to
> achieve something like this:
> {noformat}
> mimir( signature( rrf( basic() ) ) )
> {noformat}
> Flow:
> * mimir onEnter: check caches, if cache have needed payload, swap it out;
> pass on
> * signature onEnter: pass on (no op)
> * rrf onEnter: check filter rules; if ok pass on
> * basic onEnter: using transport get artifacts
> * basic onExit: validate checksums (according to policies), return result
> * rrf onExit: pass on (no op)
> * signature onExit: validate signatures of artifacts, pass on w/ failure (sig
> check result)
> * mimir onExit: check is there something new to be cached, cache it, pass on
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
