Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

GREY...GREY

Rationale

  • URI2RepositoryMapping and VirtualURIMapping have very similar goal and functionality (i.e determine which repository node to use based on a URI)
  • URI2RepositoryMapping and VirtualURIMapping have very similar interfaces, yet very different implementations and are not working "together"
  • VirtualURIMapping need overhauling to fulfill MAGNOLIA-2343@jira
  • See Proposals - overhaul and refactoring of AggregationState

Implementation ideas

  • Merging the 2 functionality under one single and clean interface
  • Using mechanisms similar to Apache's mod_rewrite: rules are executed one after the other, and each has the possibility to interrupt the chain

Possible pitfalls

  • Order of rules if configured under /modules/xyz/urimappings
  • RepositoryMappingFilter and AggregatorFilter would be merged - is there any reason why ContentSecurityFilter sits in between these 2 ?
  • No labels