Hi Tobias, I'm glad I could make things easier for you. :) I can't say I have a preference, the method to use depends on the site and its requirements. Cookies makes for cleaner routes, but from a SEO perspective it could be better to use the route way, for example. It's hard to say without knowing more about the specific site you're making.

Hi Jens, I think I'll leave that as an exercise to the reader, it should be quite easy to modify the cookie example at the end to look at the relevant headers instead of the cookie data.

Hi Pavel, glad you like the article! :) I see the problem. In this case I'd pass the "LINK" translation string/locale as page data instead, so it's definitely available.

Thank you for reading it. :) It's difficult to find a pure MVC implementation in this manner due to current trends and the ill-deserved reputation of MVC, but at least things are moving in a better direction now with Svelte for example, where a component is a decent representation of any combination of the MVC acronym. For DCI and MVC together, the Library example at https://github.com/ciscoheat/haxedci-example is at least trying to connect them, but it was 6 years ago I'm not sure if that's how I would do it today, the view part is a bit "magic", so it would be interesting to convert it to Svelte and typescript, for example. The DCI part is still pretty good though.