Hi Malte,
well, we send an "hand made" XML file to the intranet-update-client which is rendered as a HTML table.
So the user can actually decide whether to upgrade his system.
Also, we want to use the system to announce the availability of new modules (such as the wiki module recently), so that we woudln't always want to update every user to every available update.
So the process is basicly manual and gives the decision power to the user. That simplifies the code and is sufficiently flexible to deal with all kind of strange exceptions etc.
Bests,
Frank
