<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Urlshortener on Sven Ruppert</title><link>https://sven-ruppert.info/tags/urlshortener/</link><description>Recent content in Urlshortener on Sven Ruppert</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>sven.ruppert@gmail.com (Sven Ruppert)</managingEditor><webMaster>sven.ruppert@gmail.com (Sven Ruppert)</webMaster><copyright>© 2026 Sven Ruppert</copyright><lastBuildDate>Mon, 09 Feb 2026 15:15:33 +0000</lastBuildDate><atom:link href="https://sven-ruppert.info/tags/urlshortener/index.xml" rel="self" type="application/rss+xml"/><item><title>The Importance of UI in Import Processes</title><link>https://sven-ruppert.info/posts/the-importance-of-ui-in-import-processes/</link><pubDate>Mon, 09 Feb 2026 15:15:33 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/the-importance-of-ui-in-import-processes/</guid><description>&lt;h2 class="relative group"&gt;Why an import needs a UI at all
 &lt;div id="why-an-import-needs-a-ui-at-all" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-an-import-needs-a-ui-at-all" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Import functions are often treated as purely technical details in applications. Data is read in, processed and then made available – ideally without further interaction. In practice, however, an import is rarely an invisible process. It marks a transition between existing system states, between old and new data, between trust and control. This is exactly where the need for a user interface arises.&lt;/p&gt;</description></item><item><title>JSON export in Vaadin Flow</title><link>https://sven-ruppert.info/posts/20224/</link><pubDate>Thu, 05 Feb 2026 16:50:15 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/20224/</guid><description>&lt;p&gt;Export functions are often seen as a purely technical side task: one button, one download, done. In a Vaadin-based application, however, it quickly becomes apparent that exporting is much more than writing data to a file. It is a direct extension of the UI state, an infrastructural contract between frontend and backend, and a decisive factor for maintainability and predictability.&lt;/p&gt;</description></item><item><title>Introduction to the URL‑Shortener Advent Calendar 2025</title><link>https://sven-ruppert.info/posts/introduction-to-the-url%e2%80%91shortener-advent-calendar-2025/</link><pubDate>Mon, 01 Dec 2025 10:22:35 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/introduction-to-the-url%e2%80%91shortener-advent-calendar-2025/</guid><description>&lt;p&gt;December 2025 is all about a project that has grown steadily in recent months: &lt;strong&gt;the Java-based URL Shortener, an open-source project implemented entirely with Core Java, Jetty, and Vaadin Flow&lt;/strong&gt;. The Advent calendar accompanies users every day with a new feature, a technical deep dive, or an architectural improvement – from the basic data structure and REST handlers to UI components and security aspects.&lt;/p&gt;</description></item><item><title>Part II - UrlShortener - first Implementation</title><link>https://sven-ruppert.info/posts/part-ii-urlshortener-first-implementation/</link><pubDate>Fri, 20 Jun 2025 12:36:28 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/part-ii-urlshortener-first-implementation/</guid><description>&lt;h2 class="relative group"&gt;1. Introduction to implementation
 &lt;div id="1-introduction-to-implementation" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#1-introduction-to-implementation" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;

&lt;h3 class="relative group"&gt;1.1 Objectives and differentiation from the architectural part
 &lt;div id="11-objectives-and-differentiation-from-the-architectural-part" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#11-objectives-and-differentiation-from-the-architectural-part" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h3&gt;
&lt;p&gt;The first part of this series focused on theory: We explained why a URL shortener is not just a convenience tool, but a security-relevant element of digital infrastructure. We discussed models for collision detection, entropy distribution, and forwarding logic, as well as analysed architectural variants – from stateless redirect services to domain-specific validation mechanisms.&lt;/p&gt;</description></item></channel></rss>