First, we needed it. Second, I needed to create a model that would enable an instance of the server to host multiple applications, and that meant there had to be at least two apps. Third, I wanted to test whether that model would make sense to someone else. An instance of dhttp hosts one or more plug-in apps, each implemented as a Perl module with its own namespace separate from other apps and from the server. But in the case of an app, both kinds of functions are packaged into a single module.
Dynamic pages are dhttp's forte.
With these capabilities in hand, you're at the starting gate with respect to interesting and useful Web development. One of the fascinating things about dhttp is that it catapults you into that starting gate. Out of the box, conventional Web servers leave you far short of the gate. Sure, they tell you how to map Perl to the cgi-bin directory, but that's just the first step. Again it's up to you to piece together a solution.