Admin is not confused, where's the config for app foo.

No fancy rpm macro options, due layout being unified in front.

The limitation is because symlink used is %{name} which you can't override in spec. This is not hard to overcome, but it still exists.

In other words You can easily manage multiple instances of a given webapp, by simply adding another link to.

Using config load order is not needed anymore. Order in which webapps are loaded does not matter.

There's a cli program called 'webapp' which you can use to view add and remove webapp links.

Apache 1.3 and apache 2.x can have different configs, so you can create different setup for different vhosts. This is not actually a limitation.

It is open to add any webserver. lighttpd has hooks but nobody has made any config.

You can have a webapp to have subwebapp. Say horde is the main package, and horde/imp is horde module. Then the webapp name for horde-imp is “horde/imp”. The way the config symlinks are created module webapp configs are loaded before master. This allows you define /horde alias in main application and /horde/imp in sub application. It's transparent, you don't even have to think about that.

# ls -log /etc/httpd/webapps.d/drupal*.conf
lrwxrwxrwx  /etc/httpd/webapps.d/drupal-tinymce.conf ->  ../../../etc/webapps/drupal/tinymce/httpd.conf
lrwxrwxrwx  /etc/httpd/webapps.d/drupal.conf -> ../../../etc/webapps/drupal/httpd.conf

In case you have application that's not rpm package, you can achieve similiar effect. As the program to register is available outside rpm macros.