Hi Georg, On 06.01.21 10:59, Georg Kallidis wrote:
Might it be that performance is an issue? The method mapFromUrl is called only once per request, but mapToURL multiple times in a template with a lot of links.. I will check the code in more detail ...
There are possibilities for aggressive caching. I need to figure out how to balance cache size with request count, however.
Another question would be, how to know if any arbitrary TemplateURL might become friendly? We might need to add some tests more... ;-)
The whole idea is based on pattern matching. If you want to have more control over the behavior, you may as well use two different link tools in the context.
Thinking about what it is not you might agree: Achieving a more controller based routing or even providing a routing table might be not only quite some more effort, but something totally different requiring probably a complete rewrite of the pipeline valves layer. Your URLMapperService on the other side is a consistent, lightweight, and very elegant way of a URL routing mechanism in "The Turbine way". ;-)
I didn't have that in mind, initially. I wanted a non-intrusive solution. But you are right, the approach could be extended to arbitrary routing to screens and/or actions, e.g. by adding the screen class or template to the mapping configuration.
Bye, Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
